dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2024-34332

HIGH · 7.8 CVSS v3.1 Published 2024-06-10
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
An issue in SiSoftware SANDRA v31.66 (SANDRA.sys 15.18.1.1) and before allows an attacker to escalate privileges via a crafted buffer sent to the Kernel Driver using the DeviceIoControl Windows API.

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 · moderate confidence

A local privilege escalation vulnerability exists in the SANDRA.sys kernel driver (versions 15.18.1.1 and prior) in SiSoftware SANDRA v31.66 and earlier. Attackers can send crafted buffers via the DeviceIoControl Windows API to the kernel driver to elevate privileges from a low-privileged user to SYSTEM level.

MitigationUpdate SANDRA to the latest patched version once released by SiSoftware. If no patch is available, consider disabling or uninstalling the SANDRA driver to prevent exploitation, or implement application control policies to restrict access to the driver.

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 SANDRA installation directory
    Search for SiSoftware SANDRA in Program Files or Program Files (x86) directories. Typical paths include C:\Program Files\SiSoftware\Sandra or C:\Program Files (x86)\SiSoftware\Sandra. Check for a file named sandra.exe or SANDRA.exe in these locations.
    Affected if SANDRA is installed on the system in any version 31.66 or earlier, or unknown version.
  2. Identify SANDRA application version
    Right-click the sandra.exe file, select Properties, and view the File Version field in the Details tab. Alternatively, open SANDRA and check Help > About for the exact version number.
    Affected if The displayed version is 31.66 or lower, or the version cannot be determined and SANDRA is installed.
  3. Check SANDRA.sys driver file version
    Navigate to the SANDRA installation directory and locate SANDRA.sys. Right-click the file, select Properties, and view the File Version in the Details tab. This is the kernel driver version.
    Affected if The driver version is 15.18.1.1 or prior, or the driver exists but version cannot be determined.
  4. Determine if SANDRA driver is loaded
    Open an elevated command prompt or PowerShell and run: sc query SANDRA or Get-Service SANDRA. Also check Device Manager for hidden devices or use driversq to list loaded drivers. The driver may appear as a hidden/non-plug and play driver.
    Affected if The SANDRA driver service exists and is in a running state, or the driver is loaded in memory as shown by driverquery or similar enumeration.
  5. Identify the vulnerable device object
    In an elevated command prompt, run: reg query HKLM\SYSTEM\CurrentControlSet\Services\SANDRA to find the driver service parameters. The device name typically appears as \\.\SANRALite or similar device object path used by DeviceIoControl calls.
    Affected if The driver service registry entry exists and exposes a device object that accepts IOCTL requests.

If SANDRA is installed, the driver exists, and either the application version is 31.66/earlier or the driver version is 15.18.1.1/earlier, the environment is vulnerable when the driver is loaded.

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

Update SANDRA to the latest patched version once released by SiSoftware. If no patch is available, consider disabling or uninstalling the SANDRA driver to prevent exploitation, or implement application control policies to restrict access to the driver.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34332 — 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-34332 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