CVE intelligence and bounded remediation

CVE-2024-49360 — Sandboxie is a sandbox-based isolation software for 32-bit and 64-bit Windows NT-based operating systems

Critical CVSS 9.2

Sandboxie is a sandbox-based isolation software for 32-bit and 64-bit Windows NT-based operating systems. An authenticated user (**UserA**) with no privileges is authorized to read all files created in sandbox belonging to other users in the sandbox folders `C:\Sandbox\UserB\xxx`. An authenticated attacker who can use `explorer.exe` or `cmd.exe` outside any sandbox can read other users' files in `C:\Sandbox\xxx`. By default in Windows 7+, the `C:\Users\UserA` folder is not readable by **UserB**. All files edited or created during the sandbox processing are affected by the vulnerability. All files in C:\Users are safe. If `UserB` runs a cmd in a sandbox, he will be able to access `C:\Sandox\UserA`. In addition, if **UserB** create a folder `C:\Sandbox\UserA` with malicious ACLs, when **UserA** will user the sandbox, Sandboxie doesn't reset ACLs ! This issue has not yet been fixed. Users are advised to limit access to their systems using Sandboxie.

Severity
Critical
CVSS
9.2 (3.1)
Published
2024-11-29
CISA KEV
Not currently listed
Ecosystem
windows/system
Weaknesses
CWE-22

Affected products

  • sandboxie-plus / sandboxie

Showing 1 representative product identities from 2 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Path traversal, unsafe upload, and file handling

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace untrusted filenames, archive entries, URLs, and path segments into read, write, include, extraction, and upload operations.
  • Identify filesystem roots, mount permissions, symbolic-link behavior, archive handling, and whether uploaded content is web-accessible or executable.
  • Review canonicalization and containment checks across supported operating systems and storage backends.

Remediate safely

  • Generate server-side storage identifiers and resolve paths beneath a fixed root using filesystem-aware containment checks.
  • Reject absolute, parent-relative, alternate-separator, device, link, and archive entries that escape the intended root.
  • Store uploads outside executable or served paths, validate type and size, and use private atomic temporary files.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.