Strix
26.1K

CVE-2017-6903

UnknownEPSS 1.29%

Last modified

CVE-2017-6903 is a vulnerability of currently unknown severity. In ioquake3 before 2017-03-14, the auto-downloading feature has insufficient content restrictions. This also affects Quake III Arena, OpenArena, OpenJK, iortcw, and other id Tech 3 (aka Quake 3 engine) forks. EPSS estimates a 1.29% chance of exploitation in the next 30 days.

Description

In ioquake3 before 2017-03-14, the auto-downloading feature has insufficient content restrictions. This also affects Quake III Arena, OpenArena, OpenJK, iortcw, and other id Tech 3 (aka Quake 3 engine) forks. A malicious auto-downloaded file can trigger loading of crafted auto-downloaded files as native code DLLs. A malicious auto-downloaded file can contain configuration defaults that override the user's. Executable bytecode in a malicious auto-downloaded file can set configuration variables to values that will result in unwanted native code DLLs being loaded, resulting in sandbox escape.

Metrics

EPSS Probability
1.29%

66.5th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
Ioquake3Ioquake3<= 2017-02-27

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-6903?
In ioquake3 before 2017-03-14, the auto-downloading feature has insufficient content restrictions. This also affects Quake III Arena, OpenArena, OpenJK, iortcw, and other id Tech 3 (aka Quake 3 engine) forks. A malicious auto-downloaded file can trigger loading of crafted auto-downloaded files as native code DLLs. A malicious auto-downloaded file can contain configuration defaults that override the user's. Executable bytecode in a malicious auto-downloaded file can set configuration variables to values that will result in unwanted native code DLLs being loaded, resulting in sandbox escape.
How severe is CVE-2017-6903?
Severity scoring for CVE-2017-6903 is pending analysis. The EPSS model estimates a 1.29% probability of exploitation in the next 30 days.
How do I fix CVE-2017-6903?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2017

View all 2017CVEs →

Are you affected by CVE-2017-6903?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST