PatchTheCVEcube vulnerabilities and fixes
Recent CVEs affecting cube, with upgrade or downgrade steps. 4 tracked.
cube has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-03-09. Highest priority: CVE-2006-1100 (score 55/100).
- CVE-2006-1103 MEDIUM 5.0 DOWNGRADE DOWNGRADE engine/server.cpp in Sauerbraten 2006_02_28, as derived from the Cube engine, allows remote attackers to cause
- CVE-2006-1102 MEDIUM 5.0 DOWNGRADE DOWNGRADE Sauerbraten 2006_02_28, as derived from the Cube engine, allows remote attackers to cause a denial of service
- CVE-2006-1101 MEDIUM 5.0 DOWNGRADE DOWNGRADE The (1) sgetstr and (2) getint functions in Sauerbraten 2006_02_28, as derived from the Cube engine, allow rem
- CVE-2006-1100 HIGH 7.5 DOWNGRADE DOWNGRADE Buffer overflow in the sgetstr function in shared/cube.h in Sauerbraten 2006_02_28 and earlier, as derived fro
FAQ
How do I fix cube 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 cube being exploited right now?
None of the tracked cube CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which cube CVE should I patch first?
CVE-2006-1100 currently ranks highest (55/100): Buffer overflow in the sgetstr function in shared/cube.h in Sauerbraten 2006_02_28 and earlier, as derived fro.