Skip to content
Fencer Intel
critical 10.0

CVE-2011-3012 json

The ioQuake3 engine, as used in World of Padman 1.2 and earlier, Tremulous 1.1.0, and ioUrbanTerror 2007-12-20, does not check for dangerou…

published 2011-08-09 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2980

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

Summary

The ioQuake3 engine, as used in World of Padman 1.2 and earlier, Tremulous 1.1.0, and ioUrbanTerror 2007-12-20, does not check for dangerous file extensions before writing to the quake3 directory, which allows remote attackers to execute arbitrary code via a crafted third-party addon that creates a Trojan horse DLL file, a different vulnerability than CVE-2011-2764.

Patch / fix

  • ioquake3 Debian 14, Debian 13, Debian 12 1.36+svn1946-4
  • openarena Debian 14, Debian 13, Debian 12 0.8.5-5+exp1

debian advisories DEBIAN-CVE-2011-3012

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-3012 updated cvss 5.1

quake3: arbitrary code execution vulnerabilites in ioquake3

  • 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

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

Exploits and checks

  • archives.neohapsis.com http://archives.neohapsis.com/archives/fulldisclosure/2011-07/0338.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-20 Improper Input Validation

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.