CVE-2025-46715: CWE-787: Out-of-bounds Write in sandboxie-plus Sandboxie
Sandboxie is a sandbox-based isolation software for 32-bit and 64-bit Windows NT-based operating systems. Starting in version 1.3.0 and prior to version 1.15.12, Api_GetSecureParam fails to sanitize incoming pointers, and implicitly trusts that the pointer the user has passed in is safe to write to. GetRegValue then writes the contents of the SBIE registry entry selected to this address. An attacker can pass in a kernel pointer and the driver dumps the registry key contents we requested to it. This can be triggered by anyone on the system, including low integrity windows processes. Version 1.15.12 fixes the issue.
AI Analysis
Technical Summary
CVE-2025-46715 is a high-severity vulnerability classified under CWE-787 (Out-of-bounds Write) affecting Sandboxie, a sandbox-based isolation software for Windows NT-based operating systems. The flaw exists in versions starting from 1.3.0 up to but not including 1.15.12. The vulnerability arises because the function Api_GetSecureParam fails to properly sanitize incoming pointers, implicitly trusting that the pointer passed by the user is safe for writing. Specifically, the GetRegValue function writes the contents of a selected Sandboxie registry entry to the user-supplied pointer address. An attacker can exploit this by passing a kernel pointer, causing the driver to write registry key contents to arbitrary kernel memory locations. This can be triggered by any user on the system, including low integrity Windows processes, without requiring user interaction. The vulnerability allows an attacker with low privileges to perform out-of-bounds writes in kernel memory, potentially leading to privilege escalation, arbitrary code execution in kernel mode, or system instability. The issue was fixed in Sandboxie version 1.15.12. The CVSS v3.1 score is 7.8, reflecting high impact on confidentiality, integrity, and availability, with low attack complexity and requiring low privileges but no user interaction. No known exploits are currently reported in the wild, but the nature of the vulnerability makes it a significant risk if exploited.
Potential Impact
For European organizations, this vulnerability poses a serious risk, especially for those using Sandboxie for application isolation, malware analysis, or secure browsing environments. Successful exploitation could allow attackers to escalate privileges from low-integrity processes to kernel-level code execution, bypassing security controls and potentially compromising sensitive data, disrupting critical systems, or deploying persistent malware. This is particularly concerning for sectors with high security requirements such as finance, healthcare, government, and critical infrastructure. The ability for low-privilege users or malware to exploit this flaw increases the attack surface within corporate networks. Additionally, since Sandboxie is used to isolate untrusted code, a compromise here undermines the fundamental security guarantees of sandboxing, potentially allowing attackers to escape containment and affect the host system. The lack of required user interaction and the low complexity of exploitation further elevate the threat level for European enterprises relying on this software.
Mitigation Recommendations
European organizations should immediately verify their use of Sandboxie and identify any installations running versions between 1.3.0 and 1.15.11 inclusive. The primary mitigation is to upgrade Sandboxie to version 1.15.12 or later, where the vulnerability is patched. If immediate upgrade is not feasible, organizations should restrict access to Sandboxie usage to trusted users only and implement strict process and memory access controls to limit the ability of low-integrity processes to interact with the Sandboxie driver. Employing endpoint detection and response (EDR) solutions to monitor for suspicious kernel memory writes or unusual Sandboxie activity can help detect exploitation attempts. Additionally, applying the principle of least privilege to user accounts and sandboxed processes reduces the risk of exploitation. Network segmentation and application whitelisting can further limit the impact of a successful attack. Finally, organizations should stay alert for any emerging exploit code or indicators of compromise related to this CVE and update their incident response plans accordingly.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain, Poland
CVE-2025-46715: CWE-787: Out-of-bounds Write in sandboxie-plus Sandboxie
Description
Sandboxie is a sandbox-based isolation software for 32-bit and 64-bit Windows NT-based operating systems. Starting in version 1.3.0 and prior to version 1.15.12, Api_GetSecureParam fails to sanitize incoming pointers, and implicitly trusts that the pointer the user has passed in is safe to write to. GetRegValue then writes the contents of the SBIE registry entry selected to this address. An attacker can pass in a kernel pointer and the driver dumps the registry key contents we requested to it. This can be triggered by anyone on the system, including low integrity windows processes. Version 1.15.12 fixes the issue.
AI-Powered Analysis
Technical Analysis
CVE-2025-46715 is a high-severity vulnerability classified under CWE-787 (Out-of-bounds Write) affecting Sandboxie, a sandbox-based isolation software for Windows NT-based operating systems. The flaw exists in versions starting from 1.3.0 up to but not including 1.15.12. The vulnerability arises because the function Api_GetSecureParam fails to properly sanitize incoming pointers, implicitly trusting that the pointer passed by the user is safe for writing. Specifically, the GetRegValue function writes the contents of a selected Sandboxie registry entry to the user-supplied pointer address. An attacker can exploit this by passing a kernel pointer, causing the driver to write registry key contents to arbitrary kernel memory locations. This can be triggered by any user on the system, including low integrity Windows processes, without requiring user interaction. The vulnerability allows an attacker with low privileges to perform out-of-bounds writes in kernel memory, potentially leading to privilege escalation, arbitrary code execution in kernel mode, or system instability. The issue was fixed in Sandboxie version 1.15.12. The CVSS v3.1 score is 7.8, reflecting high impact on confidentiality, integrity, and availability, with low attack complexity and requiring low privileges but no user interaction. No known exploits are currently reported in the wild, but the nature of the vulnerability makes it a significant risk if exploited.
Potential Impact
For European organizations, this vulnerability poses a serious risk, especially for those using Sandboxie for application isolation, malware analysis, or secure browsing environments. Successful exploitation could allow attackers to escalate privileges from low-integrity processes to kernel-level code execution, bypassing security controls and potentially compromising sensitive data, disrupting critical systems, or deploying persistent malware. This is particularly concerning for sectors with high security requirements such as finance, healthcare, government, and critical infrastructure. The ability for low-privilege users or malware to exploit this flaw increases the attack surface within corporate networks. Additionally, since Sandboxie is used to isolate untrusted code, a compromise here undermines the fundamental security guarantees of sandboxing, potentially allowing attackers to escape containment and affect the host system. The lack of required user interaction and the low complexity of exploitation further elevate the threat level for European enterprises relying on this software.
Mitigation Recommendations
European organizations should immediately verify their use of Sandboxie and identify any installations running versions between 1.3.0 and 1.15.11 inclusive. The primary mitigation is to upgrade Sandboxie to version 1.15.12 or later, where the vulnerability is patched. If immediate upgrade is not feasible, organizations should restrict access to Sandboxie usage to trusted users only and implement strict process and memory access controls to limit the ability of low-integrity processes to interact with the Sandboxie driver. Employing endpoint detection and response (EDR) solutions to monitor for suspicious kernel memory writes or unusual Sandboxie activity can help detect exploitation attempts. Additionally, applying the principle of least privilege to user accounts and sandboxed processes reduces the risk of exploitation. Network segmentation and application whitelisting can further limit the impact of a successful attack. Finally, organizations should stay alert for any emerging exploit code or indicators of compromise related to this CVE and update their incident response plans accordingly.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-04-28T20:56:09.083Z
- Cisa Enriched
- false
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682f56360acd01a249263f60
Added to database: 5/22/2025, 4:52:06 PM
Last enriched: 7/8/2025, 9:24:56 AM
Last updated: 8/2/2025, 12:32:54 AM
Views: 22
Related Threats
CVE-2025-8464: CWE-23 Relative Path Traversal in glenwpcoder Drag and Drop Multiple File Upload for Contact Form 7
MediumCVE-2025-7499: CWE-862 Missing Authorization in wpdevteam BetterDocs – Advanced AI-Driven Documentation, FAQ & Knowledge Base Tool for Elementor & Gutenberg with Encyclopedia, AI Support, Instant Answers
MediumCVE-2025-8898: CWE-862 Missing Authorization in magepeopleteam E-cab Taxi Booking Manager for Woocommerce
CriticalCVE-2025-8896: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in cozmoslabs User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor
MediumCVE-2025-8089: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in mdempfle Advanced iFrame
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.