# CVE-2013-7039: Memory corruption in n/a

> Remote attackers can cause a crash or execute arbitrary code via a long URI in an authentication header when a specific memory limit option is set.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** Yes
- **Published:** 13 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-7039, GHSA-xjww-5jpx-q2w4

## What is CVE-2013-7039?

CVE-2013-7039 is a medium-severity memory corruption vulnerability in n/a, published on 13 Dec 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in the MHD_digest_auth_check function in libmicrohttpd before 0.9.32, when MHD_OPTION_CONNECTION_MEMORY_LIMIT is set to a large value, allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a long URI in an authentication header.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2013-7039?

It affects 1 product.


Products: Gnu Libmicrohttpd.

## How do I fix CVE-2013-7039?

Upgrade to a fixed version.

## Is CVE-2013-7039 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-59777](https://insights.sbomify.com/CVE-2025-59777/): Null dereference in GNU libbmicrohttpd (high 8.7)
- [CVE-2025-62689](https://insights.sbomify.com/CVE-2025-62689/): Null dereference in GNU libbmicrohttpd (high 8.7)
- [CVE-2013-7038](https://insights.sbomify.com/CVE-2013-7038/): Information disclosure in n/a (medium 6.4)
- [CVE-2023-27371](https://insights.sbomify.com/CVE-2023-27371/): Denial of service in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-7039 and fix it if it is affected.

What it is: CVE-2013-7039 is a medium-severity memory corruption vulnerability in n/a, published on 13 Dec 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-2013-7039 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-2013-7039/ (Markdown: https://insights.sbomify.com/CVE-2013-7039/index.md)
```

## Sources

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

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