vulnwire
7.8high

CVE-2018-5002KEVin critical feed

Adobe Flash Player versions 29.0.0.171 and earlier have a Stack-based buffer overflow vulnerability.

Published 8 y ago · modified 4 mo ago · JSON

CVSS
7.8
v3.1 · CNA
CISA KEV
Yes
added 2022-05-23
EPSS
24.4%
percentile 98%
Public exploits
0
none known

Adobe Flash Player versions 29.0.0.171 and earlier have a Stack-based buffer overflow vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.

Known exploited (CISA KEV)

Added
4 y ago
Due date
2022-06-13 (4 y ago)
Ransomware use
Unknown
Required action
The impacted product is end-of-life and should be disconnected if still in use.
Vendor / product
Adobe / Flash Player
CISA name
Adobe Flash Player Stack-based Buffer Overflow Vulnerability

CISA SSVC assessment

Exploitation
Active — exploited in the wild
Automatable
no
Technical impact
total
Assessed
11 mo ago

Exploit prediction (EPSS)

24.44% probability of exploitation in the next 30 days, higher than 98% of all scored CVEs.

CVSS scores

Assigned byVersionScoreVector
CISA ADP3.17.8CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD3.17.8CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA3.17.8CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD2.010.0AV:N/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • n/a Adobe Flash Player 29.0.0.171 and earlier versions

Classification

Weakness

References

  • access.redhat.com /errata/RHSA-2018:1827 · vendor-advisory, x_refsource_REDHAT, x_transferred
  • securitytracker.com /id/1041058 · vdb-entry, x_refsource_SECTRACK, x_transferred
  • helpx.adobe.com /security/products/flash-player/apsb18-19.html · x_refsource_MISC, x_transferred
  • security.gentoo.org /glsa/201806-02 · vendor-advisory, x_refsource_GENTOO, x_transferred
  • securityfocus.com /bid/104412 · vdb-entry, x_refsource_BID, x_transferred
  • cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-5002 · government-resource
  • github.com /cisagov/vulnrichment/issues/196 · issue-tracking

Sources

vulnwire keeps one entry per vulnerability: the CVE id wins, then GHSA; records that alias each other are merged. Machine-readable: JSON.