Credential disclosure via cross-domain redirect header forwarding
Published Mar 3, 2020 · Updated Sep 17, 2024
Credential exposure in Spring Reactor Netty 0.8.x before 0.8.16 and 0.9.x before 0.9.5 allows remote attackers to obtain credentials through redirects. When redirect following is enabled, HttpClient forwards sensitive request headers to a different domain instead of removing them. An attacker who causes a configured client to follow a cross-domain redirect can receive those credentials; clients without explicit redirect following are not exposed.
Summary
What happened
Credential exposure in Spring Reactor Netty 0.8.x before 0.8.16 and 0.9.x before 0.9.5 allows remote attackers to obtain credentials through redirects. When redirect following is enabled, HttpClient forwards sensitive request headers to a different domain instead of removing them. An attacker who causes a configured client to follow a cross-domain redirect can receive those credentials; clients without explicit redirect following are not exposed.
The record
- CVE
- CVE-2020-5404
- Published
- Mar 3, 2020
- Updated
- Sep 17, 2024
- Vendor
- Spring
- Product
- Reactor Netty
- Classifications
- CWE-522
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 3, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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.8 <v0.8.16.RELEASE
- Affected versionversion=0.9 <v0.9.5.RELEASE
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