PYSEC-2020-40
Vulnerability from pysec - Published: 2020-03-15 22:15 - Updated: 2020-03-19 17:38
VLAI?
Details
An issue was discovered in drf-jwt 1.15.x before 1.15.1. It allows attackers with access to a notionally invalidated token to obtain a new, working token via the refresh endpoint, because the blacklist protection mechanism is incompatible with the token-refresh feature. NOTE: drf-jwt is a fork of jpadilla/django-rest-framework-jwt, which is unmaintained.
Impacted products
| Name | purl | drf-jwt | pkg:pypi/drf-jwt |
|---|
Aliases
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "drf-jwt",
"purl": "pkg:pypi/drf-jwt"
},
"ranges": [
{
"events": [
{
"introduced": "1.15.0"
},
{
"fixed": "1.15.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.15.0"
]
}
],
"aliases": [
"CVE-2020-10594",
"GHSA-fpjm-rp2g-3r4c"
],
"details": "An issue was discovered in drf-jwt 1.15.x before 1.15.1. It allows attackers with access to a notionally invalidated token to obtain a new, working token via the refresh endpoint, because the blacklist protection mechanism is incompatible with the token-refresh feature. NOTE: drf-jwt is a fork of jpadilla/django-rest-framework-jwt, which is unmaintained.",
"id": "PYSEC-2020-40",
"modified": "2020-03-19T17:38:00Z",
"published": "2020-03-15T22:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://github.com/jpadilla/django-rest-framework-jwt/issues/484"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/drf-jwt/1.15.1/#history"
},
{
"type": "REPORT",
"url": "https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-fpjm-rp2g-3r4c"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…