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
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
452 | CVE-2018-1000016 | 관리자 | 2018.01.25 | 16 |
451 | CVE-2018-1000008 | 관리자 | 2018.01.25 | 16 |
450 | CVE-2017-16606 | 관리자 | 2018.01.25 | 16 |
449 | CVE-2017-16659 | 관리자 | 2017.11.09 | 16 |
448 | CVE-2017-16618 | 관리자 | 2017.11.09 | 16 |
447 | CVE-2017-14121 | 관리자 | 2017.09.04 | 16 |
446 | CVE-2017-14117 | 관리자 | 2017.09.04 | 16 |
445 | CVE-2017-12707 | 관리자 | 2017.08.27 | 16 |
444 | CVE-2017-15094 | 관리자 | 2018.01.25 | 15 |
443 | CVE-2017-18049 | 관리자 | 2018.01.25 | 15 |
442 | CVE-2018-1000003 | 관리자 | 2018.01.25 | 15 |
441 | CVE-2017-12114 | 관리자 | 2018.01.25 | 15 |
440 | CVE-2017-14095 | 관리자 | 2018.01.25 | 15 |
439 | CVE-2017-12098 | 관리자 | 2018.01.25 | 15 |
438 | CVE-2017-18044 | 관리자 | 2018.01.25 | 15 |