# CVE-2012-4465: Memory corruption in n/a

> Remote authenticated users can trigger a heap-based buffer overflow in cgit via a crafted commit author field, causing a crash or potential code execution.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-79m9-fj96-r8q8

## What is CVE-2012-4465?

CVE-2012-4465 is a medium-severity memory corruption vulnerability in n/a, published on 10 Oct 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Heap-based buffer overflow in the substr function in parsing.c in cgit 0.9.0.3 and earlier allows remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via an empty username in the "Author" field in a commit.

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

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

It affects 1 product.


Products: Lars Hjemli Cgit.

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

Upgrade to a fixed version.

## Is CVE-2012-4465 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4548](https://insights.sbomify.com/CVE-2012-4548/): Command injection in n/a (medium 6.0)
- [CVE-2011-2711](https://insights.sbomify.com/CVE-2011-2711/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4465 is a medium-severity memory corruption vulnerability in n/a, published on 10 Oct 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-4465 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-4465/ (Markdown: https://insights.sbomify.com/CVE-2012-4465/index.md)
```

## Sources

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

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