Skip to content

GHSA-5957-5crx-79jx CVE-2015-3154

Zenario CMS vulnerable to CRLF injection

Medium Packagist
Severity
6.1 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
1.01%
Chance of exploitation in the next 30 days. Higher than 63.09% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Fix
Available
3 packages have a fixed version

Description

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.

Affected versions

Packagist

PackageVulnerableFixed in
zendframework/zend-http
>= 2.0.0beta4, < 2.3.8
2.3.8
zendframework/zend-http
>= 2.4.0rc1, < 2.4.1
2.4.1
zendframework/zend-http
< 1.12.12
1.12.12
zendframework/zendframework
>= 2.0.0beta4, < 2.3.8
2.3.8
zendframework/zendframework
>= 2.4.0rc1, < 2.4.1
2.4.1
zendframework/zendframework1
< 1.12.12
1.12.12

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

zendframework/zend-http Packagist → 2.3.8

composer
composer require zendframework/zend-http:^2.3.8

zendframework/zendframework Packagist → 2.3.8

composer
composer require zendframework/zendframework:^2.3.8

zendframework/zendframework1 Packagist → 1.12.12

composer
composer require zendframework/zendframework1:^1.12.12

Severity breakdown

CVSS 3.1 6.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Weakness

CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

How to prevent it
  • Requirements: Programming languages and supporting technologies might be chosen which are not subject to these issues.
  • Implementation: Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-6fqw-j3vm-7f66
Zendframework1 Potential SQL injection in ORDER and GROUP functions
Critical Also affects zendframework/zendframework1
GHSA-848f-mph5-9pm9
Zendframework Potential Information Disclosure and Insufficient Entropy vulnerability
High Also affects zendframework/zendframework1
GHSA-8xhv-gqm4-3w99
ZendFramework1 Potential Insufficient Entropy Vulnerability
High Also affects zendframework/zendframework1
GHSA-v42g-7q2x-cw32
Zendframework1 potential SQL injection vector using null byte for PDO (MsSql, SQLite)
Critical Also affects zendframework/zendframework1
GHSA-2x36-qhx3-7m5f
ZendFramework1 Potential SQL injection in the ORDER implementation of Zend_Db_Select
Critical Also affects zendframework/zendframework1
GHSA-9v78-h226-2rmq
Zendframework potential security issue in login mechanism
High Also affects zendframework/zendframework1
GHSA-4vf6-mq7w-3hp6
Zend_Filter_StripTags vulnerable to Cross-site Scripting when comments allowed
Medium Also affects zendframework/zendframework1
GHSA-4v57-pwvf-x35j
Zendframework potential Cross-site Scripting vector in `Zend_Service_ReCaptcha_MailHide`
Medium Also affects zendframework/zendframework1
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor