Post-logout API access via unrevoked bearer token
Published Apr 28, 2020 · Updated Aug 4, 2024
Insufficient session expiration in Apache NiFi Registry 0.1.0 through 0.5.0 allows remote attackers to retain API access after logout. The logout path removes the client-side token but does not invoke a server endpoint to delete its JWT key, leaving the bearer token valid. The issue requires non-PKI authentication and possession of an issued token; replay retains that user's authorized API access for up to 12 hours.
Summary
What happened
Insufficient session expiration in Apache NiFi Registry 0.1.0 through 0.5.0 allows remote attackers to retain API access after logout. The logout path removes the client-side token but does not invoke a server endpoint to delete its JWT key, leaving the bearer token valid. The issue requires non-PKI authentication and possession of an issued token; replay retains that user's authorized API access for up to 12 hours.
The record
- CVE
- CVE-2020-9482
- Published
- Apr 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache NiFi Registry
- Classifications
- CWE-613, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=0.1.0 to 0.5.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