# CVE-2007-2047: Other in n/a

> Remote attackers can inject HTTP headers and split responses via CRLF sequences in the destination parameter of Openads.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9m52-47xr-v5f7

## What is CVE-2007-2047?

CVE-2007-2047 is a high-severity vulnerability in n/a, published on 16 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CRLF injection vulnerability in www/delivery/ck.php in Openads 2.3 (aka Max Media Manager, MMM) before 0.3.31-alpha-pr3 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the destination parameter. NOTE: some of these details are obtained from third party information.

## Which versions are affected by CVE-2007-2047?

It affects 1 product.


Products: Openads Openads.

## How do I fix CVE-2007-2047?

No fix has been published for CVE-2007-2047 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-2047 being exploited?

There is no known exploitation of CVE-2007-2047 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2008-0635](https://insights.sbomify.com/CVE-2008-0635/): Code injection in n/a (high 7.5)
- [CVE-2007-2046](https://insights.sbomify.com/CVE-2007-2046/): Other in n/a (high 7.5)
- [CVE-2007-0477](https://insights.sbomify.com/CVE-2007-0477/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2007-0363](https://insights.sbomify.com/CVE-2007-0363/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2047 and fix it if it is affected.

What it is: CVE-2007-2047 is a high-severity vulnerability in n/a, published on 16 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2047 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2007-2047/ (Markdown: https://insights.sbomify.com/CVE-2007-2047/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-2047
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-2047
- OSV: https://osv.dev/vulnerability/CVE-2007-2047

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-2047/
Summaries are generated and may contain mistakes; the official description above is the record.