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
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
212 | CVE-2015-8308 | 관리자 | 2017.08.27 | 2 |
211 | CVE-2015-7257 | 관리자 | 2017.08.27 | 2 |
210 | CVE-2017-9555 | 관리자 | 2017.08.27 | 2 |
209 | CVE-2017-12074 | 관리자 | 2017.08.27 | 2 |
208 | CVE-2017-12679 | 관리자 | 2017.08.27 | 2 |
207 | CVE-2017-9512 | 관리자 | 2017.08.27 | 2 |
» | CVE-2017-11424 | 관리자 | 2017.08.27 | 2 |
205 | CVE-2017-12136 | 관리자 | 2017.08.27 | 2 |
204 | CVE-2017-12134 | 관리자 | 2017.08.27 | 2 |
203 | CVE-2017-12137 | 관리자 | 2017.08.27 | 2 |
202 | CVE-2017-13658 (imagemagick) | 관리자 | 2017.08.27 | 2 |
201 | CVE-2017-13666 | 관리자 | 2017.08.27 | 2 |
200 | CVE-2017-0805 (android) | 관리자 | 2017.08.27 | 2 |
199 | CVE-2017-13649 | 관리자 | 2017.08.27 | 2 |
198 | CVE-2017-12847 | 관리자 | 2017.08.27 | 2 |