In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. This enables symmetric/asymmetric key confusion attacks against users using the PKCS1 PEM encoded public keys, which would allow an attacker to craft JWTs from scratch.
원문출처 : https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-11424
원문출처 : https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-11424
댓글 0
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
302 | CVE-2017-13692 | 관리자 | 2017.08.27 | 1 |
301 | CVE-2017-13695 | 관리자 | 2017.08.27 | 22 |
300 | CVE-2017-13686 | 관리자 | 2017.08.27 | 1 |
299 | CVE-2015-8355 | 관리자 | 2017.08.27 | 48 |
298 | CVE-2015-4699 | 관리자 | 2017.08.27 | 1 |
297 | CVE-2015-8352 | 관리자 | 2017.08.27 | 0 |
296 | CVE-2015-1801 | 관리자 | 2017.08.27 | 0 |
295 | CVE-2015-1800 | 관리자 | 2017.08.27 | 1 |
294 | CVE-2014-4616 | 관리자 | 2017.08.27 | 4 |
293 | CVE-2015-7516 | 관리자 | 2017.08.27 | 1 |
292 | CVE-2015-5146 | 관리자 | 2017.08.27 | 0 |
291 | CVE-2015-8308 | 관리자 | 2017.08.27 | 2 |
290 | CVE-2015-7257 | 관리자 | 2017.08.27 | 2 |
289 | CVE-2015-5293 | 관리자 | 2017.08.27 | 1 |
288 | CVE-2015-7896 | 관리자 | 2017.08.27 | 1 |