CVE-2017-6903: High severity ioquake3 ioquake3 vulnerability

Published Mar 14, 2017
·
Updated

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.

Affected Software

3 affected componentsFixes available
debian/ioquake3
1.36+u20201117.d1b7ab6~dfsg-11.36+u20221123.70d07d9+dfsg-11.36+u20240714.15f5fe7+dfsg-1
debian/iortcw
1.51.c+dfsg1-31.51.c+dfsg1-41.51.c+dfsg1-7
ioquake3 ioquake3<=2017-02-27

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/ioquake3 to a version that resolves this vulnerability.

    Fixed in 1.36+u20201117.d1b7ab6~dfsg-1Fixed in 1.36+u20221123.70d07d9+dfsg-1Fixed in 1.36+u20240714.15f5fe7+dfsg-1
  2. Upgrade

    Upgrade debian/iortcw to a version that resolves this vulnerability.

    Fixed in 1.51.c+dfsg1-3Fixed in 1.51.c+dfsg1-4Fixed in 1.51.c+dfsg1-7
  3. Compensating control

    Disable or restrict the id Tech 3 engine auto-downloading feature on ioquake3 (and affected forks: Quake III Arena, OpenArena, OpenJK, iortcw, and other id Tech 3 forks) to prevent malicious auto-downloaded configuration/scripts from overriding user settings and from triggering loading of crafted native-code DLLs.

  4. Compensating control

    Apply stricter content restrictions for auto-downloaded files in ioquake3 for all versions before 2017-03-14 to prevent executable bytecode from setting configuration variables that cause unwanted native-code DLLs to be loaded and lead to sandbox escape.

Event History

Mar 14, 2017
Data Sourced
via Debian·04:03 AM
SeverityAffected Software
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Data Sourced
via NVD·10:59 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-6903?

CVE-2017-6903 is classified as a high severity vulnerability due to the potential for remote code execution via malicious auto-downloaded files.

2

How do I fix CVE-2017-6903?

To remediate CVE-2017-6903, update ioquake3 or iortcw to their fixed versions as specified by Debian security advisories.

3

What versions of ioquake3 are affected by CVE-2017-6903?

Versions of ioquake3 prior to 2017-02-27 are affected by CVE-2017-6903.

4

What types of software are impacted by CVE-2017-6903?

CVE-2017-6903 affects ioquake3, Quake III Arena, OpenArena, OpenJK, iortcw, and other id Tech 3 forks.

5

What kind of exploit could occur due to CVE-2017-6903?

Exploiting CVE-2017-6903 could allow a malicious actor to load and execute crafted files automatically without user consent.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203