What is the CVSS score of CVE-2018-10718?

CVE-2018-10718 has a CVSS 3.0 base score of 10.0 (Critical). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 31.2%.

Is there a public PoC exploit available for CVE-2018-10718?

Yes, a public proof-of-concept exploit is available for CVE-2018-10718. Prioritise patching immediately. EPSS: 31.2%.

Call Of Duty Modern Warfare 2 CVE-2018-10718

CRITICAL

Out-of-bounds Write (CWE-787)

2018-05-03 cve@mitre.org

Memory Corruption RCE Buffer Overflow Call Of Duty Modern Warfare 2

10.0

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

10.0 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

May 03, 2018 - 18:29 nvd

CRITICAL 10.0

DescriptionNVD

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.

AnalysisAI

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. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Write (CWE-787), which allows attackers to write data beyond allocated buffer boundaries leading to code execution or crashes. 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. Affected products include: Activision Call Of Duty Modern Warfare 2. Version information: before 2018.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Validate write boundaries, use memory-safe languages, enable compiler protections (ASLR, stack canaries).