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

> Buffer overflows in FlightGear allow remote attackers to cause crashes or execute code via malicious aircraft models or UDP packets.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2091, GHSA-4p68-9fv9-q323

## What is CVE-2012-2091?

CVE-2012-2091 is a critical memory corruption vulnerability in n/a, published on 17 Jun 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple buffer overflows in FlightGear 2.6 and earlier and SimGear 2.6 and earlier allow user-assisted remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a (1) long string in a rotor tag of an aircraft xml model to the Rotor::getValueforFGSet function in src/FDM/YASim/Rotor.cpp or (2) a crafted UDP packet to the SGSocketUDP::read function in simgear/simgear/simgear/io/sg_socket_udp.cxx.

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

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

It affects 2 products.


Products: Flightgear Flightgear, Simgear Simgear.

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

Upgrade to a fixed version.

## Is CVE-2012-2091 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2090](https://insights.sbomify.com/CVE-2012-2090/): Other in n/a (critical 9.3)
- [CVE-2017-13709](https://insights.sbomify.com/CVE-2017-13709/): Path traversal in n/a (high 7.5)
- [CVE-2017-8921](https://insights.sbomify.com/CVE-2017-8921/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2091 is a critical memory corruption vulnerability in n/a, published on 17 Jun 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-2091 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-2091/ (Markdown: https://insights.sbomify.com/CVE-2012-2091/index.md)
```

## Sources

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

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