ioquake3 engine vulnerabilities and fixes
Recent CVEs affecting ioquake3 engine, with upgrade or downgrade steps. 5 tracked.
Also searched as: ioquake3engine.
ioquake3 engine has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2014-10-27. Highest priority: CVE-2011-3012 (score 64/100).
- CVE-2012-3345 MEDIUM 5.6 UPGRADE ioquake3 before r2253 allows local users to overwrite arbitrary files via a symlink attack on the /tmp/ioq3.pi
- CVE-2011-3012 HIGH 10.0 MITIGATE DOWNGRADE The ioQuake3 engine, as used in World of Padman 1.2 and earlier, Tremulous 1.1.0, and ioUrbanTerror 2007-12-20
- CVE-2011-2764 HIGH 10.0 UPGRADE MITIGATE The FS_CheckFilenameIsNotExecutable function in qcommon/files.c in the ioQuake3 engine 1.36 and earlier, as us
- CVE-2011-1412 HIGH 7.5 MITIGATE DOWNGRADE sys/sys_unix.c in the ioQuake3 engine on Unix and Linux, as used in World of Padman 1.5.x before 1.5.1.1 and O
- CVE-2010-5077 HIGH 7.8 UPGRADE MITIGATE server/sv_main.c in Quake3 Arena, as used in ioquake3 before r1762, OpenArena, Tremulous, and other products,
FAQ
How do I fix ioquake3 engine vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is ioquake3 engine being exploited right now?
None of the tracked ioquake3 engine CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which ioquake3 engine CVE should I patch first?
CVE-2011-3012 currently ranks highest (64/100): The ioQuake3 engine, as used in World of Padman 1.2 and earlier, Tremulous 1.1.0, and ioUrbanTerror 2007-12-20.