dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-55411

HIGH · 8.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 →
94/100
Remediation priority · Urgent
Remotely reachable 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
An issue in the snxpcamd.sys component of SUNIX Multi I/O Card v10.1.0.0 allows attackers to perform arbitrary read and write actions via supplying crafted IOCTL requests.

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

The snxpcamd.sys kernel-mode driver in SUNIX Multi I/O Card v10.1.0.0 contains improper access control in its IOCTL handler, allowing authenticated attackers to send crafted IOCTL requests that trigger arbitrary kernel memory read and write operations.

MitigationApply vendor-supplied driver updates when available. If no patch exists, restrict access to the affected driver device object or implement application whitelisting to prevent unauthorized IOCTL calls.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 snxpcamd.sys driver file
    Search the system for the driver file snxpcamd.sys in typical driver directories (C:\Windows\System32\drivers\ or similar paths) or use 'dir /s snxpcamd.sys' from the root directory
    Affected if The driver file snxpcamd.sys is present on the system
  2. Determine the driver version
    Right-click the driver file, select Properties, and examine the Version tab to obtain the product version; compare it against v10.1.0.0
    Affected if The installed driver version matches v10.1.0.0 or falls within the affected version range starting from v10.1.0.0
  3. Verify the driver is loaded
    Open Command Prompt as Administrator and run 'sc query snxpcamd' or check Device Manager for SUNIX Multi I/O Card devices to see if the driver is active
    Affected if The driver service state shows as RUNNING or the device appears as active in Device Manager
  4. Confirm the IOCTL handler is accessible
    Use Sysinternals tool 'winobj' or 'device tree' to locate the device object created by snxpcamd.sys (typically named \Device\snxpcamd or similar) and verify it accepts IOCTL requests
    Affected if The device object exists and is accessible, indicating the IOCTL handler is active and potentially exploitable

A system is affected if the snxpcamd.sys driver is present, installed with version v10.1.0.0, and actively loaded with its device object accessible for IOCTL operations.

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

Apply vendor-supplied driver updates when available. If no patch exists, restrict access to the affected driver device object or implement application whitelisting to prevent unauthorized IOCTL calls.

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-55411 — 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-55411 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