HTTP response splitting via unfiltered mail headers
Published Jan 27, 2020 · Updated Aug 6, 2024
CRLF injection in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to split HTTP responses. Zend\Mail header handling accepts carriage-return and line-feed sequences in untrusted field values, allowing extra headers or a header-body separator to be emitted. Exploitation requires a consuming application to place attacker-controlled email header content into an HTTP response; injected fields can alter that response.
Summary
What happened
CRLF injection in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to split HTTP responses. Zend\Mail header handling accepts carriage-return and line-feed sequences in untrusted field values, allowing extra headers or a header-body separator to be emitted. Exploitation requires a consuming application to place attacker-controlled email header content into an HTTP response; injected fields can alter that response.
The record
- CVE
- CVE-2015-3154
- Published
- Jan 27, 2020
- Updated
- Aug 6, 2024
- Vendor
- Zend
- Product
- Zend Framework
- Classifications
- CWE-74, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=2.4.x before 2.4.1
- Affected versionversion=2.x before 2.3.8
- Affected versionversion=before 1.12.12
What conditions does exploitation require?
What is affected?
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