# CVE-2008-2497: Other in n/a

> Remote attackers can inject HTTP headers and split responses in Mambo CMS, potentially leading to cache poisoning or session fixation.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xfrf-736f-2g8p

## What is CVE-2008-2497?

CVE-2008-2497 is a medium-severity vulnerability in n/a, published on 28 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CRLF injection vulnerability in Mambo before 4.6.4 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via unspecified vectors.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2008-2497?

It affects 1 product.


Products: Mambo-Foundation Mambo.

## How do I fix CVE-2008-2497?

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

## Is CVE-2008-2497 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2917](https://insights.sbomify.com/CVE-2011-2917/): SQL injection in n/a (high 7.5)
- [CVE-2008-2498](https://insights.sbomify.com/CVE-2008-2498/): SQL injection in n/a (high 7.5)
- [CVE-2011-3754](https://insights.sbomify.com/CVE-2011-3754/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2497 and fix it if it is affected.

What it is: CVE-2008-2497 is a medium-severity vulnerability in n/a, published on 28 May 2008. 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-2008-2497 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-2008-2497/ (Markdown: https://insights.sbomify.com/CVE-2008-2497/index.md)
```

## Sources

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

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