Описание
python-jose thru 3.3.0 allows JWT tokens with 'alg=none' to be decoded and accepted without any cryptographic signature verification. A malicious actor can craft a forged token with arbitrary claims (e.g., is_admin=true) and bypass authentication checks, leading to privilege escalation or unauthorized access in applications that rely on python-jose for token validation. This issue is exploitable unless developers explicitly reject 'alg=none' tokens, which is not enforced by the library.
Релиз | Статус | Примечание |
---|---|---|
devel | DNE | |
esm-apps/jammy | needs-triage | |
esm-apps/noble | needs-triage | |
jammy | needs-triage | |
noble | needs-triage | |
plucky | DNE | |
questing | DNE | |
upstream | needs-triage |
Показывать по
EPSS
6.5 Medium
CVSS3
Связанные уязвимости
python-jose thru 3.3.0 allows JWT tokens with 'alg=none' to be decoded and accepted without any cryptographic signature verification. A malicious actor can craft a forged token with arbitrary claims (e.g., is_admin=true) and bypass authentication checks, leading to privilege escalation or unauthorized access in applications that rely on python-jose for token validation. This issue is exploitable unless developers explicitly reject 'alg=none' tokens, which is not enforced by the library.
python-jose thru 3.3.0 allows JWT tokens with 'alg=none' to be decoded ...
python-jose thru 3.3.0 allows JWT tokens with 'alg=none' to be decoded and accepted without any cryptographic signature verification. A malicious actor can craft a forged token with arbitrary claims (e.g., is_admin=true) and bypass authentication checks, leading to privilege escalation or unauthorized access in applications that rely on python-jose for token validation. This issue is exploitable unless developers explicitly reject 'alg=none' tokens, which is not enforced by the library.
EPSS
6.5 Medium
CVSS3