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
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
377 | CVE-2017-12816 | 관리자 | 2017.08.27 | 7 |
376 | CVE-2017-9644 | 관리자 | 2017.08.27 | 7 |
375 | CVE-2017-0005 | 관리자 | 2017.03.18 | 7 |
374 | CVE-2017-6570 | 관리자 | 2017.03.10 | 7 |
373 | CVE-2016-6992 | 관리자 | 2016.10.14 | 7 |
372 | CVE-2016-3234 | 관리자 | 2016.06.17 | 7 |
371 | CVE-2018-5956 | 관리자 | 2018.01.25 | 6 |
370 | CVE-2018-5957 | 관리자 | 2018.01.25 | 6 |
369 | CVE-2017-7325 | 관리자 | 2018.01.25 | 6 |
368 | CVE-2017-7327 | 관리자 | 2018.01.25 | 6 |
367 | CVE-2017-1693 | 관리자 | 2018.01.25 | 6 |
366 | CVE-2018-5785 | 관리자 | 2018.01.25 | 6 |
365 | CVE-2017-16615 | 관리자 | 2017.11.09 | 6 |
364 | CVE-2017-16642 | 관리자 | 2017.11.09 | 6 |
363 | CVE-2017-2898 | 관리자 | 2017.11.09 | 6 |