Session hijacking via persistent logged-out tokens
Published May 7, 2020 · Updated Aug 4, 2024
Session hijacking in F5 Networks NGINX Controller 3.0.0 through 3.3.0 allows remote attackers to reuse a logged-out user's session token. The webserver leaves the server-side token valid after logout instead of invalidating the associated session, so possession or discovery of that token restores access. A valid token from a user who has logged out is required; reuse grants that user's Controller session privileges without affecting service availability.
Summary
What happened
Session hijacking in F5 Networks NGINX Controller 3.0.0 through 3.3.0 allows remote attackers to reuse a logged-out user's session token. The webserver leaves the server-side token valid after logout instead of invalidating the associated session, so possession or discovery of that token restores access. A valid token from a user who has logged out is required; reuse grants that user's Controller session privileges without affecting service availability.
The record
- CVE
- CVE-2020-5894
- Published
- May 7, 2020
- Updated
- Aug 4, 2024
- Vendor
- F5 Networks
- Product
- NGINX Controller
- Classifications
- CWE-384, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 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=< 3.4.0
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