Upstream PyJWT has vulnerability issue- CVE-2022-29217 Prevent key confusion through non-blocklisted public key formats. GHSA-ffqj-6fqr-9h24
envgap__AzureAD__microsoft-authentication-library-for-python-473
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
db3f1cd085e724c7b1663ae29520707a545c81a3- Manifest
setup.py- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
AzureAD/microsoft-authentication-library-for-python #473 · read the original issue
**Describe the bug** PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple different JWT signing algorithms. With JWT, an attacker submitting the JWT token can choose the used signing algorithm. The PyJWT library requires that the application chooses what algorithms are supported. The application can specify `jwt.algorithms.get_default_algorithms()` to get support for all algorithms, or specify a single algorithm. The issue is not that big as `algorithms=jwt.algorithms.get_default_algorithms()` has to be used. Users should upgrade to v2.4.0 to receive a patch for this issue. As a workaround, always be explicit with the algorithms that are accepted and expected when decoding. https://www.mend.io/vulnerability-database/CVE-2022-29217 Could you please upgrade pyjwt from 2.3.0 to 2.4.0 to fix the vulnerability.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]