LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47831: Sandboxie 5.49.7 - Denial of Service

Sandboxie 5.49.7 contains a denial of service vulnerability that allows attackers to crash the application by overflowing the container folder input field. Attackers can paste a large buffer of repeated characters into the Sandbox container folder setting to trigger an application crash.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Sandboxie 5.49.7 can be crashed by an oversized value in the container folder setting. The business impact is availability disruption of the Sandboxie application, not data theft or system takeover based on provided sources.

Executive priority

Treat as a targeted availability issue for endpoints relying on Sandboxie. Prioritize if Sandboxie supports critical workflows or security testing operations. It is not currently supported as active exploitation or data compromise in the provided evidence.

Technical view

The issue is reported as CWE-1284: improper input validation. A large container folder input can overflow handling and crash Sandboxie 5.49.7. The record assigns CVSS 3.1 score 7.5 with availability impact only. Public exploit information is referenced, but active exploitation is not supported by the provided sources.

Likely exposure

Exposure is limited to environments running Sandboxie 5.49.7, especially where users can modify Sandboxie container folder settings. The provided sources do not identify other affected versions or platforms.

Exploitation context

ExploitDB and VulnCheck reference public exploit information. However, the CVE is not marked KEV, and the provided sources do not state active exploitation in the wild. Impact appears limited to application denial of service.

Researcher notes

The source bundle shows a mismatch between the CVSS vector suggesting network, no-user-interaction attack and the description requiring pasted input into a setting. Validate assumptions against the CVE record and advisory before scoring internal risk.

Mitigation direction

  • Inventory systems for Sandboxie 5.49.7 installations.
  • Check Sandboxie vendor guidance for fixed versions or recommended configuration changes.
  • Prioritize upgrading or replacing affected installations if vendor guidance identifies a safe version.
  • Restrict who can change Sandboxie container folder settings where feasible.
  • Monitor for repeated Sandboxie crashes on affected endpoints.

Validation and detection

  • Confirm installed Sandboxie version equals 5.49.7.
  • Review endpoint software inventory for Sandboxie-Plus or Sandboxie deployments.
  • Check whether users can edit container folder settings.
  • Review crash logs for Sandboxie availability failures.
  • Compare findings with vendor and VulnCheck advisory updates.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1284: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-47831 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-47831Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Sandboxie-PlusSandboxie5.49.7Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1284 · source CWE mapping

Improper Validation of Specified Quantity in Input

Improper Validation of Specified Quantity in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.