What is the CVSS score of CVE-2015-8972?

CVE-2015-8972 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 2.4%.

Is there a public PoC exploit available for CVE-2015-8972?

Yes, a public proof-of-concept exploit is available for CVE-2015-8972. Prioritise patching immediately. EPSS: 2.4%.

Is there a patch available for CVE-2015-8972?

Yes, a patch is available for CVE-2015-8972. Update the affected software to the latest version immediately.

Chess CVE-2015-8972

CRITICAL

Buffer Overflow (CWE-119)

2017-01-23 cve@mitre.org

Buffer Overflow RCE Chess

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jan 23, 2017 - 21:59 cve.org

CRITICAL 9.8

DescriptionCVE.org

AnalysisAI

Stack-based buffer overflow in the ValidateMove function in frontend/move.cc in GNU Chess (aka gnuchess) before 6.2.4 might allow context-dependent attackers to execute arbitrary code via a large. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. Stack-based buffer overflow in the ValidateMove function in frontend/move.cc in GNU Chess (aka gnuchess) before 6.2.4 might allow context-dependent attackers to execute arbitrary code via a large input, as demonstrated when in UCI mode. Affected products include: Gnu Chess. Version information: before 6.2.4.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.