dbcve.org
Call Of Duty Modern Warfare 2Application · Activision

CVE-2018-10718

CRITICAL · 10.0 CVSS v3.0 Published 2018-05-03
Fix available
A fix is available. Upgrade to 2018-04-26 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Stack-based buffer overflow in Activision Infinity Ward Call of Duty Modern Warfare 2 before 2018-04-26 allows remote attackers to execute arbitrary code via crafted packets.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack-based buffer overflow vulnerability in Activision's Call of Duty Modern Warfare 2 allows remote attackers to execute arbitrary code by sending crafted network packets to the game client or server. The vulnerability exists in packet handling logic and can be exploited without authentication, providing complete remote code execution capability.

MitigationApply the vendor patch released after 2018-04-26. If unable to patch immediately, consider network-level filtering to restrict untrusted sources from sending game traffic, or disable multiplayer functionality until the update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Call Of Duty Modern Warfare 2Application
Affected:< 2018-04-26

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Modern Warfare 2 installation directory
    Search for the game executable (iw4sp.exe or similar main executable) on the system using file search or check common installation paths such as C:\Program Files\Activision\Call of Duty Modern Warfare 2 or C:\Program Files (x86)\Steam\steamapps\common\Call of Duty Modern Warfare 2
    Affected if The game executable is found on the system, proceed to version check. If not found, the system is not a game host for this title.
  2. Determine the installed game version
    Right-click the game executable, select Properties, and check the Details tab for file version information. Alternatively, check the game's internal version number in the main menu or launcher if the game can be launched safely in an isolated environment.
    Affected if The installed version is dated before 2018-04-26, or no version/date information is available after that date, indicating the unpatched version is present.
  3. Verify multiplayer/network functionality is enabled
    Check the game's configuration files (such as config_mp.cfg or main.ini in the game directory or user profile) for network-related settings, or inspect running processes to see if the game is listening on common game ports (UDP/27000-27030 range or typical MW2 ports).
    Affected if Multiplayer mode is enabled, the game server is running, or the system is accepting network connections for game traffic, making it vulnerable to crafted packets.
  4. Inspect network listening status
    Run netstat -an from command prompt and look for LISTENING states on UDP ports associated with the game process, or use Task Manager to identify the game process and check active network connections.
    Affected if The game process has open UDP listeners waiting for incoming connections, confirming the network attack surface is active.

The system is affected if Call of Duty Modern Warfare 2 is installed with a version predating the 2018-04-26 patch AND the game has multiplayer networking enabled or is running as a server accepting incoming connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2018-04-26 or later
Fixed in 2018-04-26
Interim mitigation

Apply the vendor patch released after 2018-04-26. If unable to patch immediately, consider network-level filtering to restrict untrusted sources from sending game traffic, or disable multiplayer functionality until the update is applied.

Recommended fix Moderate confidence

Any game version dated 2018-04-26 or later containing the security patch

  1. Apply all available game updates released on or after 2018-04-26 from the official Activision/Infinity Ward distribution platform
  2. Ensure the game server software is updated to the latest available patch that addresses this vulnerability
  3. Verify the installed version includes the security fix by checking the game client/server version number
  4. If hosting dedicated servers, ensure server operators have applied the necessary patches
Caveat Modern game patches may require compatible client versions; some older mods or third-party server tools may need updates to remain compatible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Call Of Duty Modern Warfare 2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-10718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-10718 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data