Skip to content

GHSA-h5p3-7mg6-hgj4 CVE-2012-6531

Zend Framework XEE Vulnerability

Medium Packagist
Severity
Medium
The publisher's own rating, not a CVSS score
Exploit chance (EPSS)
2.52%
Chance of exploitation in the next 30 days. Higher than 84.84% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-776 Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
Fix
1.11.13
Upgrade zendframework/zendframework1 to this version or later

Description

(1) Zend_Dom, (2) Zend_Feed, and (3) Zend_Soap in Zend Framework 1.x before 1.11.13 and 1.12.x before 1.12.0 do not properly handle SimpleXMLElement classes, which allow remote attackers to read arbitrary files or create TCP connections via an external entity reference in a DOCTYPE element in an XML-RPC request, aka an XML external entity (XXE) injection attack, a different vulnerability than CVE-2012-3363.

Affected versions

Packagist

PackageVulnerableFixed in
zendframework/zendframework1
>= 1.0, < 1.11.13
1.11.13
zendframework/zendframework1
>= 1.12.0-rc1, < 1.12.0
1.12.0

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/zendframework1 Packagist → 1.11.13

composer
composer require zendframework/zendframework1:^1.11.13

Weakness

CWE-776: Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

The product uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities.

How to prevent it
  • Operation: If possible, prohibit the use of DTDs or use an XML parser that limits the expansion of recursive DTD entities.
  • Implementation: Before parsing XML files with associated DTDs, scan for recursive entity declarations and do not continue parsing potentially explosive content.

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