dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2024-55412

HIGH · 7.8 CVSS v3.1 Published 2025-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability exits in driver snxpsamd.sys in SUNIX Serial 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in the SUNIX Serial Driver (snxpsamd.sys v10.1.0.0) allows low-privileged users to read/write arbitrary I/O ports via specially crafted IOCTL requests. This kernel-mode driver flaw enables privilege escalation to SYSTEM level, arbitrary code execution, and information disclosure. The driver is signed, allowing it to bypass Microsoft's driver-signing policy for malicious purposes.

MitigationRemove or disable the vulnerable snxpsamd.sys driver if not required; if the driver is necessary, contact SUNIX for a patched version and apply it. Consider using driver blocklisting or Windows Driver Frameworks exploit protection to prevent loading of vulnerable drivers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the snxpsamd.sys driver file
    Search for the file snxpsamd.sys on the system. Common locations include C:\Windows\System32\drivers\ and C:\Windows\SysWOW64\drivers\ for 32-bit drivers on 64-bit systems. Use PowerShell: Get-ChildItem -Path C:\ -Recurse -Filter snxpsamd.sys -ErrorAction SilentlyContinue
    Affected if The file exists on the system - the driver is present and could be loaded
  2. Determine the driver file version
    Right-click the snxpsamd.sys file, select Properties, then go to the Details tab to view the File Version. Alternatively, use PowerShell: (Get-Item 'C:\Windows\System32\drivers\snxpsamd.sys').VersionInfo.FileVersion
    Affected if The version is 10.1.0.0 exactly, as this is the vulnerable version mentioned in the summary
  3. Check if the driver is currently loaded
    Open an elevated command prompt and run: sc query snxpsamd or using PowerShell: Get-Service -Name snxpsamd -ErrorAction SilentlyContinue. Also check loaded drivers list: driverquery /v | findstr snxpsamd
    Affected if The driver shows as RUNNING or appears in the loaded drivers list - the vulnerable code is active in kernel mode
  4. Verify the driver is signed
    Right-click the snxpsamd.sys file, select Properties, then go to the Digital Signatures tab. Alternatively, use PowerShell: Get-AuthenticodeSignature 'C:\Windows\System32\drivers\snxpsamd.sys'
    Affected if The driver has a valid digital signature - this confirms it can bypass driver-signing policy and the vulnerability is exploitable as described

If snxpsamd.sys exists on the system with version 10.1.0.0 and is currently loaded/running, the environment is affected by CVE-2024-55412 and is vulnerable to privilege escalation via arbitrary I/O port access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove or disable the vulnerable snxpsamd.sys driver if not required; if the driver is necessary, contact SUNIX for a patched version and apply it. Consider using driver blocklisting or Windows Driver Frameworks exploit protection to prevent loading of vulnerable drivers.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-55412 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-55412 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data