Skip to content
Fencer Intel
critical 9.3

CVE-2012-2091 json

Multiple buffer overflows in FlightGear 2.6 and earlier and SimGear 2.6 and earlier allow user-assisted remote attackers to cause a denial…

published 2012-06-17 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2097

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.4%
EPSS 6.4% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

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.

Patch / fix

  • simgear Debian 14, Debian 13, Debian 12 2.10.0-3
  • flightgear Debian 13, Debian 12 2.6.0-1.1

debian advisories DEBIAN-CVE-2012-2091

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-2091 updated cvss 4.3

FlightGear: Stack-buffer overflow by retrieving crafted rotor name

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.39% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.