CVE-2014-0497
Memory Safety in Adobe Flash Player ≤ 11.2.202.336
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2014-0497 is a critical-severity Wrap or Wraparound (CWE-191) vulnerability in Adobe Flash Player. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.0% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and SC-18 (Mobile Code) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability CVE-2014-0497 is an integer underflow, tracked as CWE-191, in Adobe Flash Player versions before 11.7.700.261 and 11.8.x through 12.0.x before 12.0.0.44 on Windows and Mac OS X, and before 11.2.202.336 on Linux. The flaw resides in the multimedia playback component and received a CVSS 3.1 base score of 9.8.
Remote attackers can exploit the condition over the network with no authentication or user interaction required, achieving arbitrary code execution that impacts confidentiality, integrity, and availability of affected systems.
Adobe security bulletin APSB14-04 and the referenced Google Chrome stable channel update advise immediate installation of the corrected Flash Player releases; openSUSE announcements similarly direct administrators to apply the corresponding package updates to eliminate the exposure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2014-0528
Vulnerability Data
Integer underflow in Adobe Flash Player before 11.7.700.261 and 11.8.x through 12.0.x before 12.0.0.44 on Windows and Mac OS X, and before 11.2.202.336 on Linux, allows remote attackers to execute arbitrary code via unspecified vectors.
- CWE(s)
- KEV Date Added
- 17 September 2024
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires identification and installation of security-relevant software updates to eliminate the integer underflow flaw in Flash Player.
Establishes usage restrictions and security controls on mobile code technologies such as Adobe Flash that are the attack vector for this RCE.
Provides malicious-code protection mechanisms that can block or detect exploit attempts targeting the vulnerable Flash component before code execution succeeds.
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 SDLC practices directly prevent integer underflow defects via input validation, bounds checking, and static analysis.
Vulnerability scanning and code analysis can surface underflow flaws after they are introduced.
Routine patching can remediate known underflow bugs once they are discovered in deployed software.
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 catches integer underflow defects before release.
Secure development lifecycle mandates input validation and arithmetic checks that prevent integer underflow.
Application security requirements include bounds checking and safe arithmetic to avoid underflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards directly prescribe safe integer handling and overflow/underflow prevention.