CVE-2015-3113
KEVAdobe Flash Player Heap-Based Buffer Overflow Vulnerability
Description
Heap-based buffer overflow vulnerability in Adobe Flash Player allows remote attackers to execute code.
Heap-based buffer overflow in Adobe Flash Player before 13.0.0.296 and 14.x through 18.x before 18.0.0.194 on Windows and OS X and before 11.2.202.468 on Linux allows remote attackers to execute arbitrary code via unspecified vectors, as exploited in the wild in June 2015.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HPublishedJun 23, 2015
Last modifiedJun 17, 2026
Added to KEVApr 13, 2022
Remediation dueMay 4, 2022
References
- lists.opensuse.org/opensuse-security-announce/2015-06/msg00020.htmlMailing ListThird Party Advisory
- lists.opensuse.org/opensuse-security-announce/2015-06/msg00025.htmlMailing ListThird Party Advisory
- lists.opensuse.org/opensuse-security-announce/2015-07/msg00002.htmlMailing ListThird Party Advisory
- marc.info/?l=bugtraq&m=144050155601375&w=2Mailing List
- rhn.redhat.com/errata/RHSA-2015-1184.htmlThird Party Advisory
- securityfocus.com/bid/75371Broken LinkThird Party Advisory
- securitytracker.com/id/1032696Broken LinkThird Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=1235036Issue Tracking
- bugzilla.suse.com/show_bug.cgi?id=935701Issue Tracking
- h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c04952467Broken Link
- helpx.adobe.com/security/products/flash-player/apsb15-14.htmlBroken LinkPatch
- security.gentoo.org/glsa/201507-13Third Party Advisory
0 recent articles mention this CVE
89
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1637 days
- CVSS
- 9.8 CRITICAL
- EPSS (30-day exploit probability)
- 99.8% · top 1% of all CVEs
- Weakness
- CWE-787
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.The impacted product is end-of-life and should be disconnected if still in use.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.