Access bypass via unchecked disabled-user cookie
Published Jan 9, 2025 · Updated Jan 10, 2025
Insufficient session expiration in Drupal Persistent Login before 1.8.0 and 2.0.0 through 2.2.1 allows remote attackers to retain site access. During persistent-cookie validation, the module accepts a token without sufficiently checking whether its associated user account has been disabled. An unexpired cookie from a previous successful login is required, enabling a disabled account to bypass the intended access revocation.
Summary
What happened
Insufficient session expiration in Drupal Persistent Login before 1.8.0 and 2.0.0 through 2.2.1 allows remote attackers to retain site access. During persistent-cookie validation, the module accepts a token without sufficiently checking whether its associated user account has been disabled. An unexpired cookie from a previous successful login is required, enabling a disabled account to bypass the intended access revocation.
The record
- CVE
- CVE-2024-13280
- Published
- Jan 9, 2025
- Updated
- Jan 10, 2025
- Vendor
- OAuth.js
- Product
- Persistent Login
- Classifications
- CWE-613, CAPEC-87, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 9, 2025CVE publishedPublication date reported by the CVE source.
- Jan 10, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.0 <1.8.0
- Affected versionversion=2.0.* <2.2.2
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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