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-2017-6331 | 관리자 | 2017.11.09 | 181 |
196 | CVE-2017-12112 | 관리자 | 2018.01.25 | 181 |
195 | CVE-2017-0007 | 관리자 | 2017.03.18 | 182 |
194 | CVE-2016-3212 | 관리자 | 2016.06.17 | 183 |
193 | CVE-2017-0018 | 관리자 | 2017.03.18 | 183 |
192 | CVE-2015-7529 | 관리자 | 2017.11.09 | 183 |
191 | CVE-2017-14029 | 관리자 | 2017.11.09 | 183 |
190 | CVE-2017-2911 | 관리자 | 2017.11.09 | 183 |
189 | CVE-2017-16659 | 관리자 | 2017.11.09 | 183 |
188 | CVE-2016-0028 | 관리자 | 2016.06.17 | 184 |
187 | CVE-2016-3214 | 관리자 | 2016.06.17 | 184 |
186 | CVE-2017-0030 | 관리자 | 2017.03.18 | 184 |
185 | CVE-2018-5785 | 관리자 | 2018.01.25 | 184 |
184 | CVE-2017-1000416 | 관리자 | 2018.01.25 | 184 |
183 | CVE-2017-16598 | 관리자 | 2018.01.25 | 184 |