You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to dependency file: /Linux/Python/requirements.txt
Path to vulnerable library: /tmp/ws-ua_20250114023736_VDGCJZ/python_FESKPX/202501140257071/env/lib/python3.8/site-packages/PyJWT-1.7.1.dist-info,/tmp/ws-ua_20250114023736_VDGCJZ/python_FESKPX/202501140302441/env/lib/python3.8/site-packages/PyJWT-1.7.1.dist-info,/tmp/ws-ua_20250114023736_VDGCJZ/python_FESKPX/202501140246161/env/lib/python3.8/site-packages/PyJWT-1.7.1.dist-info,/tmp/ws-ua_20250114023736_VDGCJZ/python_FESKPX/202501140251421/env/lib/python3.8/site-packages/PyJWT-1.7.1.dist-info,/tmp/ws-ua_20250114023736_VDGCJZ/python_FESKPX/202501140237371/env/lib/python3.8/site-packages/PyJWT-1.7.1.dist-info
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.
Use of vulnerable components will introduce weaknesses into the application. Components with published vulnerabilities will allow easy exploitation as resources will often be available to automate the process.
CVE-2022-29217 - High Severity Vulnerability
Vulnerable Library - PyJWT-1.7.1-py2.py3-none-any.whl
JSON Web Token implementation in Python
Library home page: https://files.pythonhosted.org/packages/87/8b/6a9f14b5f781697e51259d81657e6048fd31a113229cf346880bb7545565/PyJWT-1.7.1-py2.py3-none-any.whl
Path to dependency file: /Linux/Python/requirements.txt
Path to vulnerable library: /tmp/ws-ua_20250114023736_VDGCJZ/python_FESKPX/202501140257071/env/lib/python3.8/site-packages/PyJWT-1.7.1.dist-info,/tmp/ws-ua_20250114023736_VDGCJZ/python_FESKPX/202501140302441/env/lib/python3.8/site-packages/PyJWT-1.7.1.dist-info,/tmp/ws-ua_20250114023736_VDGCJZ/python_FESKPX/202501140246161/env/lib/python3.8/site-packages/PyJWT-1.7.1.dist-info,/tmp/ws-ua_20250114023736_VDGCJZ/python_FESKPX/202501140251421/env/lib/python3.8/site-packages/PyJWT-1.7.1.dist-info,/tmp/ws-ua_20250114023736_VDGCJZ/python_FESKPX/202501140237371/env/lib/python3.8/site-packages/PyJWT-1.7.1.dist-info
Dependency Hierarchy:
Found in HEAD commit: 282db09a8dda8b4c4d0ff56875195546b18b0ec5
Found in base branch: master
Vulnerability Details
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 asalgorithms=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.Publish Date: 2022-05-24
URL: CVE-2022-29217
CVSS 3 Score Details (7.4)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29217
Release Date: 2022-05-24
Fix Resolution: PyJWT - 2.4.0
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: