Skip to content

GHSA-229x-22xc-2f2w

Zendframework Local file disclosure via XXE injection in Zend_XmlRpc

High Packagist
Severity
8.6 / 10
High · CVSS 3.1
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-611 Improper Restriction of XML External Entity Reference
Fix
1.11.13
Upgrade zendframework/zendframework1 to this version or later

Description

Zend_XmlRpc is vulnerable to XML eXternal Entity (XXE) Injection attacks. The SimpleXMLElement class (SimpleXML PHP extension) is used in an insecure way to parse XML data. External entities can be specified by adding a specific DOCTYPE element to XML-RPC requests. By exploiting this vulnerability an application may be coerced to open arbitrary files and/or TCP connections.

Affected versions

Packagist

PackageVulnerableFixed in
zendframework/zendframework1
>= 1.0.0, < 1.11.13
1.11.13

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

Severity breakdown

CVSS 3.1 8.6

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

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

Weakness

CWE-611: Improper Restriction of XML External Entity Reference

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How to prevent it
  • Implementation, System Configuration: Many XML parsers and validators can be configured to disable external entity expansion.

References

Timeline

  1. Published
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