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
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
407 | CVE-2017-0031 | 관리자 | 2017.03.18 | 8 |
406 | CVE-2017-0075 | 관리자 | 2017.03.18 | 8 |
405 | CVE-2017-0074 | 관리자 | 2017.03.18 | 8 |
404 | CVE-2017-0067 | 관리자 | 2017.03.18 | 8 |
403 | CVE-2017-0049 | 관리자 | 2017.03.18 | 8 |
402 | CVE-2017-0082 | 관리자 | 2017.03.18 | 8 |
401 | CVE-2017-0097 | 관리자 | 2017.03.18 | 8 |
400 | CVE-2017-0079 | 관리자 | 2017.03.18 | 8 |
399 | CVE-2017-0087 | 관리자 | 2017.03.18 | 8 |
398 | CVE-2017-0085 | 관리자 | 2017.03.18 | 8 |
397 | CVE-2017-0076 | 관리자 | 2017.03.18 | 8 |
396 | CVE-2017-0099 | 관리자 | 2017.03.18 | 8 |
395 | CVE-2017-0104 | 관리자 | 2017.03.18 | 8 |
394 | CVE-2017-0130 | 관리자 | 2017.03.18 | 8 |
393 | CVE-2017-0125 | 관리자 | 2017.03.18 | 8 |