Kernel crash via integer-wrapped pool allocation
Published May 22, 2025 · Updated May 22, 2025
Pool buffer overflow in Sandboxie 1.3.0 through 1.15.11 allows local users to crash Windows or execute code in the kernel. The SbieDrv.sys API_GET_SECURE_PARAM handler stores a WCHAR name length in a 32-bit ULONG; a huge caller-controlled name wraps the allocation size before wcscpy copies the full string into the undersized pool buffer. Low-integrity processes can reach the driver API, and the proof of concept triggers a PAGE_FAULT_IN_NONPAGED_AREA crash; arbitrary code execution is identified as the worst case, but its exploitability remains unresolved.
Summary
What happened
Pool buffer overflow in Sandboxie 1.3.0 through 1.15.11 allows local users to crash Windows or execute code in the kernel. The SbieDrv.sys API_GET_SECURE_PARAM handler stores a WCHAR name length in a 32-bit ULONG; a huge caller-controlled name wraps the allocation size before wcscpy copies the full string into the undersized pool buffer. Low-integrity processes can reach the driver API, and the proof of concept triggers a PAGE_FAULT_IN_NONPAGED_AREA crash; arbitrary code execution is identified as the worst case, but its exploitability remains unresolved.
The record
- CVE
- CVE-2025-46714
- Published
- May 22, 2025
- Updated
- May 22, 2025
- Vendor
- Sandboxie-Plus
- Product
- Sandboxie
- Classifications
- CWE-120, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 22, 2025CVE publishedPublication date reported by the CVE source.
- May 22, 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=>= 1.3.0, < 1.15.12
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
- Upstream API_GET_SECURE_PARAM crash 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