Resource access via unchecked inactive-user token creation
Published Mar 16, 2024 · Updated Nov 1, 2024
Improper privilege management in djangorestframework-simplejwt before 5.5.1 allows attackers to access protected resources as inactive users. The Token.for_user method creates a JWT for an inactive user without checking is_active, leaving validation to the calling application. Reachability requires custom token issuance and authentication code that omits the active-status checks provided by the standard serializers and JWTAuthentication backend.
Summary
What happened
Improper privilege management in djangorestframework-simplejwt before 5.5.1 allows attackers to access protected resources as inactive users. The Token.for_user method creates a JWT for an inactive user without checking is_active, leaving validation to the calling application. Reachability requires custom token issuance and authentication code that omits the active-status checks provided by the standard serializers and JWTAuthentication backend.
The record
- CVE
- CVE-2024-22513
- Published
- Mar 16, 2024
- Updated
- Nov 1, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-306, CWE-269, T1550.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 16, 2024CVE publishedPublication date reported by the CVE source.
- Nov 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Inactive-user token proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo