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-2017-0088 | 관리자 | 2017.03.18 | 10 |
436 | CVE-2017-0100 | 관리자 | 2017.03.18 | 14 |
435 | CVE-2017-0090 | 관리자 | 2017.03.18 | 21 |
434 | CVE-2017-0101 | 관리자 | 2017.03.18 | 18 |
433 | CVE-2017-0092 | 관리자 | 2017.03.18 | 15 |
432 | CVE-2017-0102 | 관리자 | 2017.03.18 | 14 |
431 | CVE-2017-0079 | 관리자 | 2017.03.18 | 19 |
430 | CVE-2017-0103 | 관리자 | 2017.03.18 | 26 |
429 | CVE-2017-0083 | 관리자 | 2017.03.18 | 20 |
428 | CVE-2017-0105 | 관리자 | 2017.03.18 | 21 |
427 | CVE-2017-0087 | 관리자 | 2017.03.18 | 20 |
426 | CVE-2017-0107 | 관리자 | 2017.03.18 | 21 |
425 | CVE-2017-0091 | 관리자 | 2017.03.18 | 15 |
424 | CVE-2017-0108 | 관리자 | 2017.03.18 | 57 |
423 | CVE-2017-0081 | 관리자 | 2017.03.18 | 22 |