Continued account access via unrevoked session tokens
Published Aug 3, 2023 · Updated Oct 10, 2024
Insufficient session expiration in Apache Answer before 1.1.0 allows remote authenticated users to retain account access after a password change. Password-update paths change the stored password but do not remove existing access tokens from the per-user cache mapping. A valid token issued before the password change remains usable, preserving the session's existing account privileges.
Summary
What happened
Insufficient session expiration in Apache Answer before 1.1.0 allows remote authenticated users to retain account access after a password change. Password-update paths change the stored password but do not remove existing access tokens from the per-user cache mapping. A valid token issued before the password change remains usable, preserving the session's existing account privileges.
The record
- CVE
- CVE-2023-4126
- Published
- Aug 3, 2023
- Updated
- Oct 10, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Answer
- Classifications
- CWE-613, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 3, 2023CVE publishedPublication date reported by the CVE source.
- Oct 10, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <v1.1.0
What conditions does exploitation require?
What is affected?
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.
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