# GHSA-jmmp-vh96-78rm: Zend-Feed URL Rewrite vulnerability

> Attackers can spoof HTTP headers to bypass URL rewrite logic and request arbitrary internal content via SSRF in Zend libraries.

- **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-jmmp-vh96-78rm?

GHSA-jmmp-vh96-78rm is a server-side request forgery vulnerability in zendframework/zend-feed, 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-diactoros (and, by extension, Expressive), zend-http (and, by extension, Zend Framework MVC projects), and zend-feed (specifically, its PubSubHubbub sub-component) each contain a potential URL rewrite exploit. In each case, marshaling a request URI includes logic that introspects HTTP request headers that are specific to a given server-side URL rewrite mechanism.

When these headers are present on systems not running the specific URL rewriting mechanism, the logic would still trigger, allowing a malicious client or proxy to emulate the headers to request arbitrary content.

## Which versions are affected by GHSA-jmmp-vh96-78rm?

2 open source packages ship an affected version, including zendframework/zend-feed.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zendframework/zend-feed` | Packagist | From 1.0.0 | 2.10.3 |
| `zendframework/zend-feed` | Packagist | From 1.0.0 | 2.10.3 |

## How do I fix GHSA-jmmp-vh96-78rm?

Upgrade zendframework/zend-feed to 2.10.3 or later.

## Is GHSA-jmmp-vh96-78rm being exploited?

There is no known exploitation of GHSA-jmmp-vh96-78rm in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-jmmp-vh96-78rm and fix it if it is affected.

What it is: GHSA-jmmp-vh96-78rm is a server-side request forgery vulnerability in zendframework/zend-feed, 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-jmmp-vh96-78rm in the wild and no public exploit code.

Affected packages and fixed versions:
- zendframework/zend-feed (Packagist): affected from 1.0.0; fixed in 2.10.3
- zendframework/zend-feed (Packagist): affected from 1.0.0; fixed in 2.10.3

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-jmmp-vh96-78rm/ (Markdown: https://insights.sbomify.com/GHSA-jmmp-vh96-78rm/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-jmmp-vh96-78rm

---
From sbomify Insights: https://insights.sbomify.com/GHSA-jmmp-vh96-78rm/
Summaries are generated and may contain mistakes; the official description above is the record.