Skip to main content
VulnerabilityPublished Updated

CVE-2024-55413: SUNIX Parallel Driver x64 - · Out-of-bounds Write

Source CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediately audit systems to identify installations of SUNIX Parallel Driver version 10.1.0.0 on Windows x64 platforms.
  2. Restrict access to systems running this driver to trusted personnel only, minimizing the risk of local exploitation.
  3. Employ application whitelisting and endpoint protection solutions that can detect and block unauthorized IOCTL requests or suspicious driver behavior.
  4. Monitor system logs and security events for unusual IOCTL activity or attempts to access I/O ports.
  5. Use Windows security features such as Device Guard and Credential Guard to limit the impact of driver-level exploits.
  6. Engage with SUNIX or vendor support channels to obtain patches or updated driver versions as soon as they become available.
  7. Consider deploying kernel-mode exploit mitigation technologies like Kernel Patch Protection (PatchGuard) and Driver Signature Enforcement (DSE) with enhanced monitoring.
  8. Implement strict privilege management policies to limit the number of users with local access and low privileges that could exploit this vulnerability.
  9. For environments where immediate patching is not possible, isolate affected systems from critical networks to reduce lateral movement risk.
  10. Regularly update and test incident response plans to quickly address potential exploitation scenarios involving driver vulnerabilities.

Description

A vulnerability exits in driver snxppamd.sys in SUNIX Parallel Driver x64 - 10.1.0.0, which allows low-privileged users to read and write arbitary i/o port via specially crafted IOCTL requests . This can be exploited for privilege escalation, code execution under high privileges, and information disclosure. These signed drivers can also be used to bypass the Microsoft driver-signing policy to deploy malicious code.

References

Community reviews

Loading reviews…