Account access via reusable leaked CSRF token
Published Jan 21, 2020 · Updated Aug 4, 2024
Cross-site request forgery in Red Hat Quay 2.x before 3.0.0 allows remote attackers to access the service as a user via a leaked token. The web GUI places its _csrf_token in POST parameters, exposes it in some query strings, and reuses it across logout and subsequent login sessions. Exploitation requires obtaining a user's leaked token and inducing user interaction; successful use inherits that account's access.
Summary
What happened
Cross-site request forgery in Red Hat Quay 2.x before 3.0.0 allows remote attackers to access the service as a user via a leaked token. The web GUI places its _csrf_token in POST parameters, exposes it in some query strings, and reuses it across logout and subsequent login sessions. Exploitation requires obtaining a user's leaked token and inducing user interaction; successful use inherits that account's access.
The record
- CVE
- CVE-2019-3864
- Published
- Jan 21, 2020
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- Red Hat Quay
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 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=all quay-2 versions before quay-3.0.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