GHSA-f4fj-q6m4-cc52 ZendFramework vulnerable to XXE/XEE attacks
Not scored
Published
Check this codebase for GHSA-f4fj-q6m4-cc52 and fix it if it is affected.
What it is: GHSA-f4fj-q6m4-cc52 is a vulnerability in zendframework/zend-xmlrpc, published on 7 Jun 2024. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-f4fj-q6m4-cc52 in the wild and no public exploit code.
Affected packages and fixed versions:
- zendframework/zend-xmlrpc (Packagist): affected from 2.1.0; fixed in 2.1.6
- zendframework/zend-xmlrpc (Packagist): affected from 2.1.0; fixed in 2.1.6
- zendframework/zend-xmlrpc (Packagist): affected from 2.2.0; fixed in 2.2.6
- zendframework/zend-xmlrpc (Packagist): affected from 2.2.0; fixed in 2.2.6
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/GHSA-f4fj-q6m4-cc52/ (Markdown: https://insights.sbomify.com/GHSA-f4fj-q6m4-cc52/index.md)
Zend Framework components are vulnerable to XXE and XEE attacks, allowing attackers to read arbitrary files or cause denial of service via malicious XML input.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-f4fj-q6m4-cc52?
GHSA-f4fj-q6m4-cc52 is a vulnerability in zendframework/zend-xmlrpc, published on 7 Jun 2024. It can be exploited over the network, with no action from the victim.
Official description
Numerous components utilizing PHP's DOMDocument, SimpleXML, and xml_parse functionality are vulnerable to two types of attacks:
- XML eXternal Entity (XXE) Injection attacks. The above mentioned extensions are insecure by default, allowing external entities to be specified by adding a specific DOCTYPE element to XML documents and strings. By exploiting this vulnerability an application may be coerced to open arbitrary files and/or TCP connections.
- XML Entity Expansion (XEE) vectors, leading to Denial of Service vectors. XEE attacks occur when the XML DOCTYPE declaration includes XML entity definitions that contain either recursive or circular references; this leads to CPU and memory consumption, making Denial of Service exploits trivial to implement.
Which versions are affected by GHSA-f4fj-q6m4-cc52?
4 open source packages ship an affected version, including zendframework/zend-xmlrpc.
| Package | Affected | Fixed in |
|---|---|---|
zendframework/zend-xmlrpc Packagist | From 2.1.0 | 2.1.6 |
zendframework/zend-xmlrpc Packagist | From 2.1.0 | 2.1.6 |
zendframework/zend-xmlrpc Packagist | From 2.2.0 | 2.2.6 |
zendframework/zend-xmlrpc Packagist | From 2.2.0 | 2.2.6 |
How do I fix GHSA-f4fj-q6m4-cc52?
Upgrade zendframework/zend-xmlrpc to a fixed version for your release line: 2.1.6 or 2.2.6.
Is GHSA-f4fj-q6m4-cc52 being exploited?
There is no known exploitation of GHSA-f4fj-q6m4-cc52 in the wild and no public exploit code.