{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46715 exists.","fix":"No fix has been published for CVE-2025-46715 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46715 is a high-severity memory corruption vulnerability in sandboxie-plus Sandboxie, published on 22 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46715 and fix it if it is affected.\n\nWhat it is: CVE-2025-46715 is a high-severity memory corruption vulnerability in sandboxie-plus Sandboxie, published on 22 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46715 exists.\n\nAffected product: sandboxie-plus Sandboxie. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-46715/ (Markdown: https://insights.sbomify.com/CVE-2025-46715/index.md)","id":"CVE-2025-46715","markdown":"https://insights.sbomify.com/CVE-2025-46715/index.md","name":"CVE-2025-46715","record":{"aliases":["GHSA-67p9-6h73-ff7x"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows sandbox software","requires_auth":"low_privilege","summary":"A local attacker can exploit a kernel driver flaw to write arbitrary data to kernel memory, leading to privilege escalation or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sandboxie","vendor":"sandboxie-plus"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Sandboxie Arbitrary Kernel Write in SbieDrv.sys API (API_GET_SECURE_PARAM)","id":"CVE-2025-46715","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Sandboxie Arbitrary Kernel Read in SbieDrv.sys API (API_SET_SECURE_PARAM)","id":"CVE-2025-46716"},"packages":[],"prev":{"headline":"Sandboxie has Pool Buffer Overflow in SbieDrv.sys API (API_GET_SECURE_PARAM)","id":"CVE-2025-46714"},"products":["Sandboxie"],"published":"2025-05-22","related":[{"cvss_score":10,"headline":"Security feature bypass in n/a","id":"CVE-2018-18748","kev_date_added":null,"published":"2018-10-28"},{"cvss_score":9.9,"headline":"Sandboxie's Integer Overflow in SbieIniServer::RC4Crypt allows sandbox escape and SYSTEM compromise","id":"CVE-2025-64721","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":9.3,"headline":"Sandboxie-Plus privilege escalation via INI CRLF injection bypassing EditAdminOnly","id":"CVE-2026-34458","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":9.2,"headline":"Path traversal in Sandboxie","id":"CVE-2024-49360","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":8.8,"headline":"Sandboxie-Plus sandbox escape via uninitialized memory leak and stack overflow in GetRawInputDeviceInfoSlave","id":"CVE-2026-34459","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.8,"headline":"Sandboxie-Plus NamedPipeServer OpenHandler stack overflow via unterminated server field","id":"CVE-2026-34464","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.2,"headline":"Sandboxie kernel driver denial of service via malformed IOCTL from sandboxed process","id":"CVE-2026-32603","kev_date_added":null,"published":"2026-05-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-22","vendors":["sandboxie-plus"]},"summary":"A local attacker can exploit a kernel driver flaw to write arbitrary data to kernel memory, leading to privilege escalation or code execution.","url":"https://insights.sbomify.com/CVE-2025-46715/"}