IRONSMITHINTEL
HIGHCVSS7.8
|
Actively Exploited
|CISA KEV|CVE-2018-5002|Auth: none — unauthenticated|Reboot: required|Manual only

Adobe Flash Player Stack-based Buffer Overflow Vulnerability

Adobe Flash Player have a stack-based buffer overflow vulnerability that could lead to remote code execution.

Published Jul 9, 2018 · Updated May 16, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A local attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2022-06-13 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Out-of-bounds Write (CWE-787) vulnerability in Adobe Flash Player. Exploitation requires local access, low attack complexity, no authentication required, and user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

Endpoint Administrators
IT Security
Running flash player desktop runtime: v ≤ 29.0.0.171; flash player: v ≤ 29.0.0.171; enterprise linux desktop: 6.0; enterprise linux server: 6.0; enterprise linux workstation: 6.0
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2022-05-23 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2022-06-13.

How to patch

Manual remediation steps

Apply the Vendor Patch

This vulnerability is in the CISA Known Exploited Vulnerabilities catalog — apply the vendor's security update as soon as possible.

CISA required action: The impacted product is end-of-life and should be disconnected if still in use.

References

    1
    Vendor advisory: https://helpx.adobe.com/security/products/flash-player/apsb18-19.html
    1
    NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2018-5002
    1
    CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-5002
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.