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

> Buffer overflows in Condor allow attackers to potentially execute arbitrary code or cause denial of service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 28 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-5196, GHSA-2cx2-wv26-jp38

## What is CVE-2012-5196?

CVE-2012-5196 is a critical memory corruption vulnerability in n/a, published on 28 Sep 2012. 

### Official description

Multiple buffer overflows in Condor 7.6.x before 7.6.10 and 7.8.x before 7.8.4 have unknown impact and attack vectors.

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

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

It affects 1 product.


Products: Condor Project Condor.

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

Upgrade to a fixed version.

## Is CVE-2012-5196 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5390](https://insights.sbomify.com/CVE-2012-5390/): Privilege escalation in n/a (critical 10.0)
- [CVE-2012-5197](https://insights.sbomify.com/CVE-2012-5197/): Other in n/a (critical 10.0)
- [CVE-2012-3416](https://insights.sbomify.com/CVE-2012-3416/): Auth bypass in n/a (critical 10.0)
- [CVE-2008-3424](https://insights.sbomify.com/CVE-2008-3424/): Auth bypass in n/a (high 7.5)
- [CVE-2008-3830](https://insights.sbomify.com/CVE-2008-3830/): Auth bypass in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5196 is a critical memory corruption vulnerability in n/a, published on 28 Sep 2012. 
Exploitation: There is no known exploitation of CVE-2012-5196 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-5196/ (Markdown: https://insights.sbomify.com/CVE-2012-5196/index.md)
```

## Sources

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

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