Skip to content
Fencer Intel
critical 9.3

CVE-2011-4620 in the critical feed json

Buffer overflow in the ulSetError function in util/ulError.cxx in PLIB 1.8.5, as used in TORCS 1.3.1 and other products, allows user-assist…

published 2011-12-31 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4543

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
12.6%
EPSS 12.6% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

Buffer overflow in the ulSetError function in util/ulError.cxx in PLIB 1.8.5, as used in TORCS 1.3.1 and other products, allows user-assisted remote attackers to execute arbitrary code via vectors involving a long error message, as demonstrated by a crafted acc file for TORCS. NOTE: some of these details are obtained from third party information.

Patch / fix

  • plib Debian 14, Debian 13, Debian 12 1.8.5-5.1

debian advisories DEBIAN-CVE-2011-4620

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-2011-4620 updated cvss 4.1

plib ulSetError() buffer overflow

  • 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

Timeline

  1. First public exploit (EDB-18258)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-18258 TORCS 1.3.1 - acc Buffer Overflow local, 2011-12-20

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.