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
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
437 | CVE-2018-5958 | 관리자 | 2018.01.25 | 29 |
436 | CVE-2017-7325 | 관리자 | 2018.01.25 | 29 |
435 | CVE-2018-1362 | 관리자 | 2018.01.25 | 29 |
434 | CVE-2018-5786 | 관리자 | 2018.01.25 | 29 |
433 | CVE-2017-14025 | 관리자 | 2017.11.09 | 29 |
432 | CVE-2017-16570 | 관리자 | 2017.11.09 | 29 |
431 | CVE-2017-9805 | 관리자 | 2017.09.16 | 29 |
430 | CVE-2017-14118 | 관리자 | 2017.09.04 | 29 |
429 | CVE-2014-7857 | 관리자 | 2017.08.27 | 29 |
428 | CVE-2015-4180 | 관리자 | 2017.08.27 | 29 |
427 | CVE-2015-7896 | 관리자 | 2017.08.27 | 29 |
426 | CVE-2016-3220 | 관리자 | 2016.06.17 | 29 |
425 | CVE-2017-15094 | 관리자 | 2018.01.25 | 28 |
424 | CVE-2018-1000016 | 관리자 | 2018.01.25 | 28 |
423 | CVE-2018-1000015 | 관리자 | 2018.01.25 | 28 |