# GHSA-2jx7-xg83-j2m7: Zendframework Denial of Service vector via XEE injection

> Attackers can cause Denial of Service in Zend Framework components via XML Entity Expansion attacks, affecting applications processing untrusted XML.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jun 2024

## What is GHSA-2jx7-xg83-j2m7?

GHSA-2jx7-xg83-j2m7 is a denial of service vulnerability in zendframework/zendframework1, published on 7 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

`Zend_Dom`, `Zend_Feed`, `Zend_Soap`, and `Zend_XmlRpc` are vulnerable to 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-2jx7-xg83-j2m7?

2 open source packages ship an affected version, including zendframework/zendframework1.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zendframework/zendframework1` | Packagist | From 1.0.0 | 1.11.13 |
| `zendframework/zendframework1` | Packagist | From 1.0.0 | 1.11.13 |

## How do I fix GHSA-2jx7-xg83-j2m7?

Upgrade zendframework/zendframework1 to 1.11.13 or later.

## Is GHSA-2jx7-xg83-j2m7 being exploited?

There is no known exploitation of GHSA-2jx7-xg83-j2m7 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2jx7-xg83-j2m7 and fix it if it is affected.

What it is: GHSA-2jx7-xg83-j2m7 is a denial of service vulnerability in zendframework/zendframework1, published on 7 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-2jx7-xg83-j2m7 in the wild and no public exploit code.

Affected packages and fixed versions:
- zendframework/zendframework1 (Packagist): affected from 1.0.0; fixed in 1.11.13
- zendframework/zendframework1 (Packagist): affected from 1.0.0; fixed in 1.11.13

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-2jx7-xg83-j2m7/ (Markdown: https://insights.sbomify.com/GHSA-2jx7-xg83-j2m7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2jx7-xg83-j2m7

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2jx7-xg83-j2m7/
Summaries are generated and may contain mistakes; the official description above is the record.