dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-29513

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
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 briscKernelDriver.sys in BlueRiSC WindowsSCOPE Cyber Forensics before 3.3 allows a local attacker to execute arbitrary code within the driver and create a local denial-of-service condition due to an improper DACL being applied to the device the driver creates.

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 briscKernelDriver.sys driver creates a device object with an improperly configured DACL (Discretionary Access Control List), allowing any local user to open handles to the device and send IOCTL requests. This enables local privilege escalation to execute arbitrary code in kernel context, plus the ability to cause a denial of service by sending malformed or malicious requests to the driver.

MitigationApply a restrictive DACL to the device object during driver initialization, granting access only to Administrators or SYSTEM, and validate all IOCTL inputs in the driver dispatch routines to prevent abuse.

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. Verify briscKernelDriver.sys presence
    Search for the file briscKernelDriver.sys in driver directories (C:\Windows\System32\drivers or similar) or check loaded drivers via 'driverquery /v' or 'Get-ProcessModule' in PowerShell
    Affected if The driver file exists on the system or is listed as a loaded driver in memory
  2. Identify the device object name
    Use tools like WinObj, Process Explorer, or 'fltmc instances' to enumerate device objects created by the driver. Look for \Device\brisc* or similar device names
    Affected if A device object associated with briscKernelDriver.sys exists on the system
  3. Inspect the device object DACL
    Use 'sdutil.exe <device_name>' or PowerShell 'Get-Acl \Device\brisc* | fl' to examine the security descriptor. Alternatively, use Sysinternals 'accesschk.exe -d \Device\brisc*' to report effective permissions
    Affected if The DACL grants read or write access to Users, Everyone, or other non-privileged groups rather than restricting to Administrators and SYSTEM only
  4. Test handle acquisition from low-privilege context
    Run a command as a standard user (non-admin): 'handle.exe brisc' or attempt CreateFile() on the device path from a low-privilege process to verify handle opening succeeds
    Affected if A non-admin user can successfully obtain a handle to the device object

If briscKernelDriver.sys is loaded and its device object DACL permits access by non-privileged users, the system is vulnerable to local privilege escalation via this flaw.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply a restrictive DACL to the device object during driver initialization, granting access only to Administrators or SYSTEM, and validate all IOCTL inputs in the driver dispatch routines to prevent abuse.

Recommended fix Moderate confidence

BlueRiSC WindowsSCOPE Cyber Forensics version 3.3

  1. Verify the current installed version of BlueRiSC WindowsSCOPE Cyber Forensics
  2. Download the updated version 3.3 or later from the official vendor source
  3. Uninstall the current version of WindowsSCOPE Cyber Forensics
  4. Install the updated version 3.3 which contains the patched briscKernelDriver.sys with proper DACL configuration
  5. Reboot the system to ensure the new driver is properly loaded
  6. Verify the driver version and that the device object now has correct DACL settings using tools like WinObj or icacls
Caveat Kernel driver updates may require system reboot and could affect forensic tool functionality during the update process

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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