# CVE-2012-5875: Null dereference in n/a

> Remote attackers can cause a denial of service in Firefly Media Server by sending crafted HTTP headers or protocol versions.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 18 Jan 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-x639-58w5-52jj

## What is CVE-2012-5875?

CVE-2012-5875 is a medium-severity vulnerability in n/a, published on 18 Jan 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Firefly Media Server 1.0.0.1359 allows remote attackers to cause a denial of service (NULL pointer dereference) via a (1) crafted Connection HTTP header; a return carriage control character in the (2) Accept Language header, (3) User-agent header, (4) Host header, or (5) protocol version; or a (6) crafted HTTP protocol version.

## Which versions are affected by CVE-2012-5875?

It affects 1 product.


Products: Fireflymediaserver Firefly Media Server.

## How do I fix CVE-2012-5875?

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

## Is CVE-2012-5875 being exploited?

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

Public exploit code:

- FireFly Mediaserver 1.0.0.1359 - Null Pointer Dereference (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5875 and fix it if it is affected.

What it is: CVE-2012-5875 is a medium-severity vulnerability in n/a, published on 18 Jan 2013. 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-2012-5875 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-2012-5875/ (Markdown: https://insights.sbomify.com/CVE-2012-5875/index.md)
```

## Sources

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

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