PatchTheCVEurbanterror vulnerabilities
Recent CVEs affecting urbanterror products. 2 tracked.
urbanterror has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2011-08-09. Highest priority: CVE-2011-3012 (score 64/100).
- 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
FAQ
How do I fix urbanterror 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 urbanterror being exploited right now?
None of the tracked urbanterror CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which urbanterror 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.