Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2015-3113 is a critical-severity Out-of-bounds Write (CWE-787) vulnerability in Adobe Flash Player. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.0% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2015-3113 is a heap-based buffer overflow vulnerability, also described under CWE-787 and CWE-122, that affects Adobe Flash Player versions before 13.0.0.296 and 14.x through 18.x before 18.0.0.194 on Windows and OS X, as well as versions before 11.2.202.468 on Linux. The flaw resides in the handling of unspecified input vectors that trigger out-of-bounds memory writes.
Remote attackers can exploit the issue over the network with no authentication or user interaction required beyond rendering malicious content, resulting in arbitrary code execution on the target system. The vulnerability received a CVSS 3.1 base score of 9.8 reflecting its critical impact on confidentiality, integrity, and availability.
Multiple vendor advisories, including those from openSUSE and Red Hat, direct administrators to apply the corresponding Flash Player updates referenced in their respective errata to eliminate the vulnerable code paths. The issue was observed being exploited in the wild during June 2015.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2015-3194
Vulnerability Data
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…
more
in June 2015.
- CWE(s)
- KEV Date Added
- 13 April 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.