CVE-2015-3154: CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows…
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 63.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: zendframework (Debian:6.0) 1.10.6-1squeeze3; zendframework (Debian:7) 1.11.13-1.1+deb7u1; zendframework/zend-http (Packagist) 2.3.8, 2.4.1, 1.12.12.
Low priority for now. Upgrade to zendframework (Debian:6.0) 1.10.6-1squeeze3; zendframework (Debian:7) 1.11.13-1.1+deb7u1; zendframework/zend-http (Packagist) 2.3.8, 2.4.1, 1.12.12 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
CRLF injection vulnerability in Zend\Mail (Zend_Mail) 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 inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
- Published
- Jan 27, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 63th percentile
- CWE
- CWE-74
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| zend | zend framework | cpe:2.3:a:zend:zend_framework |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Zend Technologies Zend Framework
- before 1.12.12, 2.x before 2.3.8, 2.4.x before 2.4.1affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zend zend frameworkbefore 1.12.12
- zend zend framework2.3.0 and later · before 2.3.8
- zend zend framework2.4.0 and later · before 2.4.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:6.0 | zendframework | before 1.10.6-1squeeze3 | 1.10.6-1squeeze3 |
| Debian:7 | zendframework | before 1.11.13-1.1+deb7u1 | 1.11.13-1.1+deb7u1 |
| Packagist | zendframework/zend-http | from 2.0.0beta4 · before 2.3.8 | 2.3.8 |
| Packagist | zendframework/zend-http | from 2.4.0rc1 · before 2.4.1 | 2.4.1 |
| Packagist | zendframework/zend-http | before 1.12.12 | 1.12.12 |
| Packagist | zendframework/zendframework | from 2.0.0beta4 · before 2.3.8 | 2.3.8 |
| Packagist | zendframework/zendframework | from 2.4.0rc1 · before 2.4.1 | 2.4.1 |
| Packagist | zendframework/zendframework1 | before 1.12.12 | 1.12.12 |
Same product
zend: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3007Laminas Project laminas-http before 2.14.2, and Zend Framework 3.0.0, has a deserialization vulnerability that can lead to remote code…62This week
- CVE-2016-10034The setFrom function in the Sendmail adapter in the zend-mail component before 2.4.11, 2.5.x, 2.6.x, and 2.7.x before 2.7.2, and Zend…51Plan
- CVE-2012-3363Zend_XmlRpc in Zend Framework 1.x before 1.11.12 and 1.12.x before 1.12.0 does not properly handle SimpleXMLElement classes, which allows…51Plan
Published before and after this one in the same product
- ← EarlierCVE-2014-4913Dec 15, 2019 · ZF2014-03 has a potential cross site scripting vector in multiple view helpers24Monitor
- ← EarlierCVE-2012-4451Jan 3, 2020 · Multiple cross-site scripting (XSS) vulnerabilities in Zend Framework 2.0.x before 2.0.1 allow remote attackers to inject arbitrary web…24Monitor
- Later →CVE-2014-8089Feb 17, 2020 · SQL injection vulnerability in Zend Framework before 1.12.9, 2.2.x before 2.2.8, and 2.3.x before 2.3.3, when using the sqlsrv PHP…40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:zendframework | 1.10.6-1squeeze3 · Debian:6.0 | Package registry (OSV) |
| Packagist:zendframework/zend-http | 1.12.12 | Package registry (OSV) |
| Packagist:zendframework/zend-http | 2.3.8 | Package registry (OSV) |
| Packagist:zendframework/zend-http | 2.4.1 | Package registry (OSV) |
| Packagist:zendframework/zendframework | 2.3.8 | Package registry (OSV) |
| Packagist:zendframework/zendframework | 2.4.1 | Package registry (OSV) |
| Packagist:zendframework/zendframework1 | 1.12.12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- HTTP Request SplittingCAPEC-105likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Format String InjectionCAPEC-135likelihood: High · High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →