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
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
197 | CVE-2018-5957 | 관리자 | 2018.01.25 | 156 |
196 | CVE-2017-14803 | 관리자 | 2018.01.25 | 156 |
195 | CVE-2017-14025 | 관리자 | 2017.11.09 | 156 |
194 | CVE-2017-9805 | 관리자 | 2017.09.16 | 156 |
193 | CVE-2017-13671 | 관리자 | 2017.08.27 | 156 |
192 | CVE-2017-7410 | 관리자 | 2017.04.04 | 156 |
191 | CVE-2017-13141 (imagemagick) | 관리자 | 2017.08.27 | 155 |
190 | CVE-2017-0090 | 관리자 | 2017.03.18 | 155 |
189 | CVE-2017-0094 | 관리자 | 2017.03.18 | 155 |
188 | CVE-2017-6576 (mail-masta) | 관리자 | 2017.03.10 | 155 |
187 | CVE-2017-6575 | 관리자 | 2017.03.10 | 155 |
186 | CVE-2018-1000002 | 관리자 | 2018.01.25 | 154 |
185 | CVE-2017-16635 | 관리자 | 2017.11.09 | 154 |
184 | CVE-2016-3231 | 관리자 | 2016.06.17 | 154 |
183 | CVE-2014-7857 | 관리자 | 2017.08.27 | 153 |