CVE-2024-12547
Memory Safety in Tungstenautomation Power Pdf ≤ 5.1.1.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-12547 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Tungstenautomation Power Pdf. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — 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.
CVE-2024-12547 is an out-of-bounds write vulnerability in the JPF file parsing component of Tungsten Automation Power PDF, enabling remote code execution. The issue stems from a lack of proper validation of user-supplied data within JPF files, resulting in a write past the end of an allocated object. This flaw affects installations of Tungsten Automation Power PDF and was disclosed as ZDI-CAN-25560.
Remote attackers can exploit the vulnerability by inducing a target user to visit a malicious web page or open a malicious file, as user interaction is required. No privileges are needed (PR:N), and exploitation occurs over the network (AV:N) with low complexity (AC:L). Successful attacks allow arbitrary code execution in the context of the current process, with impacts including high confidentiality, integrity, and availability (C:H/I:H/A:H). The vulnerability carries a CVSS v3.1 base score of 8.8 and maps to CWE-787 (Out-of-bounds Write).
Details on the vulnerability, including mitigation recommendations, are provided in the Zero Day Initiative advisory ZDI-24-1681 at https://www.zerodayinitiative.com/advisories/ZDI-24-1681/.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-50947
Vulnerability Data
Tungsten Automation Power PDF JPF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Tungsten Automation Power PDF. User interaction is required to exploit this vulnerability in that…
more
the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of JPF files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25560.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.
Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.
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 (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
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.