← Back
CVE-2017-6903
high
CVSS 7.8
Vulnerability in ioquake3 (CVE-2017-6903)
Summary
vulnerability in ioquake3 (CVE-2017-6903). Successful exploitation can lead to full system takeover.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2017-6903** has been found in ioquake3.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "ioquake3 CVE-2017-6903" on the vendor's site.
CVE-2017-6903 (ioquake3) — CVSS v3 7.8
Attack vector: local / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (unclassified) exists in ioquake3.
📍 Affected scope
ioquake3 — .
🔥 Severity
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'ioquake3' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ioquake3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ioquake3` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory http://www.debian.org/security/2017/dsa-3812
- advisory https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857699
- advisory https://ioquake3.org/2017/03/13/important-security-update-please-update-ioquake3-immediately/
- patch https://github.com/JACoders/OpenJK/commit/8956a35e7b91c4a0dd1fa6db1d28c7f0efbab2d7
- patch https://github.com/ioquake/ioq3/commit/376267d534476a875d8b9228149c4ee18b74a4fd
- patch https://github.com/ioquake/ioq3/commit/b173ac05993f634a42be3d3535e1b158de0c3372
- patch https://github.com/ioquake/ioq3/commit/f61fe5f6a0419ef4a88d46a128052f2e8352e85d
- patch https://github.com/iortcw/iortcw/commit/11a83410153756ae350a82ed41b08d128ff7f998
- patch https://github.com/iortcw/iortcw/commit/b248763e4878ef12d5835ece6600be8334f67da1
- patch https://github.com/iortcw/iortcw/commit/b6ff2bcb1e4e6976d61e316175c6d7c99860fe20