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

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

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

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

Protobuf CVE-2015-5237

HIGH

Out-of-bounds Write (CWE-787)

2017-09-25 secalert@redhat.com

GHSA-jwvw-v7c5-m82h

Buffer Overflow Memory Corruption Protobuf

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/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:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Sep 25, 2017 - 17:29 cve.org

HIGH 8.8

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

5 pypi packages depend on protobuf (5 direct, 0 indirect)

Ecosystem-wide dependent count for version 3.4.0.

DescriptionCVE.org

protobuf allows remote authenticated attackers to cause a heap-based buffer overflow.

AnalysisAI

protobuf allows remote authenticated attackers to cause a heap-based buffer overflow. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. This Out-of-bounds Write vulnerability could allow attackers to write data beyond allocated buffer boundaries leading to code execution or crashes.

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. protobuf allows remote authenticated attackers to cause a heap-based buffer overflow. Affected products include: Google Protobuf.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate write boundaries, use memory-safe languages, enable compiler protections (ASLR, stack canaries).