Post-logout data access via persistent authorization tokens
Published Jul 23, 2024 · Updated Sep 13, 2024
Insufficient session expiration in Apache StreamPark 1.0.0 through 2.1.3 allows attackers to access data with a logged-out token. The Backend returns an Authorization token after login, but the logout path does not invalidate that credential, so it remains accepted for later requests. Exploitation requires possession of a token issued by a successful login and permits continued request submission and data access after logout.
Summary
What happened
Insufficient session expiration in Apache StreamPark 1.0.0 through 2.1.3 allows attackers to access data with a logged-out token. The Backend returns an Authorization token after login, but the logout path does not invalidate that credential, so it remains accepted for later requests. Exploitation requires possession of a token issued by a successful login and permits continued request submission and data access after logout.
The record
- CVE
- CVE-2024-29070
- Published
- Jul 23, 2024
- Updated
- Sep 13, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache StreamPark
- Classifications
- CWE-613, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2024CVE publishedPublication date reported by the CVE source.
- Sep 13, 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=1.0.0 <2.1.4
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.
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