Response header injection via unsanitized CORS ExposeHeader
Published Jun 26, 2020 · Updated Aug 4, 2024
HTTP response splitting in Red Hat Ceph Storage 3.x and 4.x allows remote attackers to inject arbitrary headers through an S3 CORS request. RGWCORSRule::format_exp_headers appends ExposeHeader values from an S3 CORS XML document to Access-Control-Expose-Headers without escaping newline characters. Exploitation requires a crafted CORS configuration and a user's cross-origin request, after which injected headers can alter the browser-visible response.
Summary
What happened
HTTP response splitting in Red Hat Ceph Storage 3.x and 4.x allows remote attackers to inject arbitrary headers through an S3 CORS request. RGWCORSRule::format_exp_headers appends ExposeHeader values from an S3 CORS XML document to Access-Control-Expose-Headers without escaping newline characters. Exploitation requires a crafted CORS configuration and a user's cross-origin request, after which injected headers can alter the browser-visible response.
The record
- CVE
- CVE-2020-10753
- Published
- Jun 26, 2020
- Updated
- Aug 4, 2024
- Vendor
- 389 Directory Server
- Product
- Red Hat Ceph Storage
- Classifications
- CWE-113, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 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=versions 3.x and 4.x
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