PyJWT Project PyJWT 0.3.2

CPE Details

PyJWT Project PyJWT 0.3.2
pyjwt_project
pyjwt
0.3.2
2019-12-10
18h19 +00:00
2019-12-10
18h19 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:pyjwt_project:pyjwt:0.3.2:*:*:*:*:*:*:*

Informations

Vendor

pyjwt_project

Product

pyjwt

Version

0.3.2

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2017-11424 2017-08-24 14h00 +00:00 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.
7.5
High
The information presented on CVE Find originates from several carefully selected reference sources. CVE data is provided by MITRE Corporation and the National Vulnerability Database (NVD). The Known Exploited Vulnerabilities (KEV) catalog is sourced from the Cybersecurity and Infrastructure Security Agency (CISA), while EPSS scores come from FIRST.org. Additionally, data regarding software weaknesses (CWE) and common attack patterns (CAPEC) is maintained by MITRE Corporation, and information on hardware and software configurations (CPE) is provided by the NVD.