CVE-2017-11424 Affecting python-jwt package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL7-PYTHONJWT-4416742
- published1 Nov 2021
- disclosed22 Jun 2017
Introduced: 22 Jun 2017
CVE-2017-11424 (opens in a new tab)How to fix?
There is no fixed version for RHEL:7 python-jwt.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python-jwt package and not the python-jwt package as distributed by RHEL.
See How to fix? for RHEL:7 relevant fixed versions and status.
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.