Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2011-3012

The ioQuake3 engine, as used in World of Padman 1.2 and earlier, Tremu ...

Overview

Published
9 Aug 2011
Modified
29 Apr 2026
High CVE
0 Registry packages
2 OS packages
3 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

10 · HIGH

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Weakness: CWE-20

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 15 fixes

debian 4 releases · 2 packages

fixed 8
openarena ioquake3
debian fixes for CVE-2011-3012
ReleasePackageFixed in
11 openarena 0.8.5-5+exp1
11 ioquake3 1.36+svn1946-4
12 openarena 0.8.5-5+exp1
12 ioquake3 1.36+svn1946-4
13 openarena 0.8.5-5+exp1
13 ioquake3 1.36+svn1946-4

2 more rows

echo 1 release · 2 packages

fixed 2
openarena ioquake3
echo fixes for CVE-2011-3012
ReleasePackageFixed in
openarena 0.8.5-5+exp1
ioquake3 1.36+svn1946-4

ubuntu 5 releases · 1 package

affected 5
ioquake3
ubuntu fixes for CVE-2011-3012
ReleasePackageFixed in
18.04-ESM ioquake3 affected
20.04-ESM ioquake3 affected
22.04 ioquake3 affected
24.04 ioquake3 affected
26.04 ioquake3 affected

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.