CVE-2025-5099
Published: 23 May 2025
Summary
CVE-2025-5099 is a critical-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Dynamixsoftware Printershare. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 22.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
An out-of-bounds write vulnerability, tracked as CVE-2025-5099 and also associated with CWE-119 and CWE-787, affects a native library during PDF rendering. The flaw can produce memory corruption that leads to arbitrary code execution and is rated 9.8 under CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
An unauthenticated attacker can trigger the issue remotely over the network with no user interaction required, enabling memory corruption and potential arbitrary code execution on the target system.
Public advisories referenced at https://korelogic.com/Resources/Advisories/KL-001-2025-004.txt describe the condition.
The EPSS score remains flat at a low 0.0104 with no material rise observed after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-28382
Vulnerability details
An Out of Bounds Write occurs when the native library attempts PDF rendering, which can be exploited to achieve memory corruption and potentially arbitrary code execution.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
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.
Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.