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-9805 | 관리자 | 2017.09.16 | 18 |
466 | CVE-2017-14100 | 관리자 | 2017.09.04 | 18 |
465 | CVE-2017-9650 | 관리자 | 2017.08.27 | 18 |
464 | CVE-2017-7410 | 관리자 | 2017.04.04 | 18 |
463 | CVE-2016-3220 | 관리자 | 2016.06.17 | 18 |
462 | CVE-2017-2742 | 관리자 | 2018.01.25 | 17 |
461 | CVE-2018-1000011 | 관리자 | 2018.01.25 | 17 |
460 | CVE-2018-1000008 | 관리자 | 2018.01.25 | 17 |
459 | CVE-2018-1042 | 관리자 | 2018.01.25 | 17 |
458 | CVE-2017-12119 | 관리자 | 2018.01.25 | 17 |
457 | CVE-2017-16645 | 관리자 | 2017.11.09 | 17 |
456 | CVE-2017-14119 | 관리자 | 2017.09.04 | 17 |
455 | CVE-2017-14121 | 관리자 | 2017.09.04 | 17 |
454 | CVE-2017-14117 | 관리자 | 2017.09.04 | 17 |
453 | CVE-2017-14116 | 관리자 | 2017.09.04 | 17 |