# CVE-2012-4999: Denial of service in n/a

> Remote attackers can cause a denial of service on Mercury MR804 routers by sending crafted HTTP header fields.

- **Severity:** Medium 6.1 (`AV:A/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p5jq-469q-mxmf

## What is CVE-2012-4999?

CVE-2012-4999 is a medium-severity denial of service vulnerability in n/a, published on 19 Sep 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mercury MR804 Router 8.0 3.8.1 Build 101220 Rel.53006nB allows remote attackers to cause a denial of service (service hang) via a crafted string in HTTP header fields such as (1) If-Modified-Since, (2) If-None-Match, or (3) If-Unmodified-Since.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Mercurycom Mr804, Mercurycom Mr804 Firmware.

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

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

## Is CVE-2012-4999 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4999 exists.

Public exploit code:

- Mercury MR804 Router - Multiple HTTP Header Fields Denial of Service Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4999 is a medium-severity denial of service vulnerability in n/a, published on 19 Sep 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4999 exists.

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

## Sources

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

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