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

CVE-2018-4936 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. EPSS exploitation probability: 29.1%.

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

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

Is there a patch available for CVE-2018-4936?

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

Flash Player CVE-2018-4936

MEDIUM

Buffer Overflow (CWE-119)

2018-05-19 psirt@adobe.com

Buffer Overflow Information Disclosure Adobe Flash Player Flash Player Desktop Runtime

6.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

May 19, 2018 - 17:29 nvd

MEDIUM 6.5

DescriptionNVD

Adobe Flash Player versions 29.0.0.113 and earlier have an exploitable Heap Overflow vulnerability. Successful exploitation could lead to information disclosure.

AnalysisAI

Adobe Flash Player versions 29.0.0.113 and earlier have an exploitable Heap Overflow vulnerability. Rated medium severity (CVSS 6.5), 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. Adobe Flash Player versions 29.0.0.113 and earlier have an exploitable Heap Overflow vulnerability. Successful exploitation could lead to information disclosure. Affected products include: Adobe Flash Player Desktop Runtime, Adobe Flash Player.

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.