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
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
422 | CVE-2017-18046 | 관리자 | 2018.01.25 | 14 |
421 | CVE-2017-12112 | 관리자 | 2018.01.25 | 14 |
420 | CVE-2017-1693 | 관리자 | 2018.01.25 | 14 |
419 | CVE-2017-16660 | 관리자 | 2017.11.09 | 14 |
418 | CVE-2017-16644 | 관리자 | 2017.11.09 | 14 |
417 | CVE-2017-16650 | 관리자 | 2017.11.09 | 14 |
416 | CVE-2017-2917 | 관리자 | 2017.11.09 | 14 |
415 | CVE-2017-16570 | 관리자 | 2017.11.09 | 14 |
414 | CVE-2017-12857 | 관리자 | 2017.08.27 | 14 |
413 | CVE-2015-1324 | 관리자 | 2017.08.27 | 14 |
412 | CVE-2017-9506 | 관리자 | 2017.08.27 | 14 |
411 | CVE-2017-11159 | 관리자 | 2017.08.27 | 14 |
410 | CVE-2017-5684 | 관리자 | 2017.04.04 | 14 |
409 | CVE-2017-0127 | 관리자 | 2017.03.18 | 14 |
408 | CVE-2017-0143 | 관리자 | 2017.03.18 | 14 |