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-12119 | 관리자 | 2018.01.25 | 17 |
466 | CVE-2017-12116 | 관리자 | 2018.01.25 | 19 |
465 | CVE-2017-12113 | 관리자 | 2018.01.25 | 564 |
464 | CVE-2017-14460 | 관리자 | 2018.01.25 | 11 |
463 | CVE-2017-14457 | 관리자 | 2018.01.25 | 20 |
462 | CVE-2017-12112 | 관리자 | 2018.01.25 | 13 |
461 | CVE-2017-12117 | 관리자 | 2018.01.25 | 11 |
460 | CVE-2017-12114 | 관리자 | 2018.01.25 | 16 |
459 | CVE-2017-12115 | 관리자 | 2018.01.25 | 12 |
458 | CVE-2017-12097 | 관리자 | 2018.01.25 | 11 |
457 | CVE-2017-14094 | 관리자 | 2018.01.25 | 12 |
456 | CVE-2017-14096 | 관리자 | 2018.01.25 | 12 |
455 | CVE-2017-14095 | 관리자 | 2018.01.25 | 15 |
454 | CVE-2017-14097 | 관리자 | 2018.01.25 | 13 |
453 | CVE-2017-14082 | 관리자 | 2018.01.25 | 8 |