Authentication-flow manipulation via unchecked OAuth2 state
Published Feb 27, 2020 · Updated Sep 16, 2024
CSRF in Cloud Foundry Foundation UAA before 74.14.0 allows remote attackers to manipulate external-provider authentication. The external identity provider callback accepts an OAuth2 response without comparing its state parameter with the value bound to the initiating browser session. Exploitation requires user interaction and a configured external identity provider; the vendor does not further detail the resulting account or session impact.
Summary
What happened
CSRF in Cloud Foundry Foundation UAA before 74.14.0 allows remote attackers to manipulate external-provider authentication. The external identity provider callback accepts an OAuth2 response without comparing its state parameter with the value bound to the initiating browser session. Exploitation requires user interaction and a configured external identity provider; the vendor does not further detail the resulting account or session impact.
The record
- CVE
- CVE-2020-5402
- Published
- Feb 27, 2020
- Updated
- Sep 16, 2024
- Vendor
- Cloud Foundry Foundation
- Product
- User Account and Authentication (UAA)
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 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 <v74.14.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