CVE-2022-28067
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn incorrect access control issue in Sandboxie Classic v5.55.13 allows attackers to cause a Denial of Service (DoS) in the Sandbox via a crafted executable.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSandboxie Classic v5.55.13 contains an incorrect access control vulnerability that allows a specially crafted executable to bypass sandbox restrictions and cause a Denial of Service within the sandboxed environment. The flaw appears to stem from insufficient validation of executable behavior within the sandbox isolation mechanism.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.55.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Sandboxie Classic installationCheck if Sandboxie Classic is installed by looking for the program in Add/Remove Programs, or by searching for Sandboxie.exe in typical installation paths such as C:\Program Files\Sandboxie or C:\Program Files (x86)\SandboxieAffected if Sandboxie Classic is not found on the system, then this CVE does not apply
-
Identify installed Sandboxie versionRight-click the Sandboxie icon in the system tray and select About, or open the Sandboxie Control panel and check the version information displayedAffected if The installed version is exactly 5.55.13, indicating the vulnerable version is present
-
Confirm Sandboxie service is activeOpen Windows Services (services.msc) and locate the Sandboxie service, or check if the Sandboxie icon appears in the system tray indicating the service is runningAffected if Sandboxie service is running and the version is 5.55.13, making the environment affected by this vulnerability
-
Review sandbox configuration for untrusted executablesOpen Sandboxie Manager, select each sandbox, and inspect the applied restrictions and any explicitly allowed programs listed in the sandbox settingsAffected if The sandbox permits execution of untrusted or unspecified executables while running the vulnerable 5.55.13 version
The environment is affected if Sandboxie Classic version 5.55.13 is installed and the Sandboxie isolation service is active, regardless of specific sandbox configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Sandboxie Classic to the latest patched version that addresses the access control vulnerability. If no patched version is available, restrict execution of untrusted executables within the sandbox and monitor for anomalous behavior.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28067 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data