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
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
467 | CVE-2017-14023 | 관리자 | 2017.11.09 | 199 |
466 | CVE-2017-11159 | 관리자 | 2017.08.27 | 199 |
465 | CVE-2018-0845 | 관리자 | 2018.01.25 | 198 |
464 | CVE-2017-12096 | 관리자 | 2017.11.09 | 198 |
463 | CVE-2017-0056 | 관리자 | 2017.03.18 | 198 |
462 | CVE-2017-6952 | 관리자 | 2017.03.18 | 198 |
461 | CVE-2017-6578 (mail-masta) | 관리자 | 2017.03.10 | 198 |
460 | CVE-2017-6570 | 관리자 | 2017.03.10 | 198 |
459 | CVE-2017-17406 | 관리자 | 2018.01.25 | 197 |
458 | CVE-2017-16604 | 관리자 | 2018.01.25 | 197 |
457 | CVE-2017-0059 | 관리자 | 2017.03.18 | 197 |
456 | CVE-2018-5955 | 관리자 | 2018.01.25 | 196 |
455 | CVE-2017-16645 | 관리자 | 2017.11.09 | 196 |
454 | CVE-2017-16564 | 관리자 | 2017.11.09 | 196 |
453 | CVE-2017-13692 | 관리자 | 2017.08.27 | 196 |