Local privilege escalation via permissive driver DACL
Published May 13, 2024 · Updated Feb 13, 2025
Improper access control in BlueRISC WindowsSCOPE Cyber Forensics before 3.3 allows local users to execute code in the kernel. The driver creates the \.\BriscKernel device with IoCreateDevice rather than a secure creation routine, granting Everyone write access to IOCTLs that perform privileged memory operations. A low-privilege local account can misuse those operations for kernel-context code execution or send malformed data to IOCTL 0x222028 to bugcheck the host.
Summary
What happened
Improper access control in BlueRISC WindowsSCOPE Cyber Forensics before 3.3 allows local users to execute code in the kernel. The driver creates the \.\BriscKernel device with IoCreateDevice rather than a secure creation routine, granting Everyone write access to IOCTLs that perform privileged memory operations. A low-privilege local account can misuse those operations for kernel-context code execution or send malformed data to IOCTL 0x222028 to bugcheck the host.
The record
- CVE
- CVE-2024-29513
- Published
- May 13, 2024
- Updated
- Feb 13, 2025
- Vendor
- BlueRISC
- Product
- WindowsSCOPE Cyber Forensics
- Classifications
- CWE-94, T1068, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- briscKernelDriver.sys IOCTL denial-of-service proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo