LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32773: Confused deputy attack in sandbox module resolution

Racket is a general-purpose programming language and an ecosystem for language-oriented programming. In versions prior to 8.2, code evaluated using the Racket sandbox could cause system modules to incorrectly use attacker-created modules instead of their intended dependencies. This could allow system functions to be controlled by the attacker, giving access to facilities intended to be restricted. This problem is fixed in Racket version 8.2. A workaround is available, depending on system settings. For systems that provide arbitrary Racket evaluation, external sandboxing such as containers limit the impact of the problem. For multi-user evaluation systems, such as the `handin-server` system, it is not possible to work around this problem and upgrading is required.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Racket sandboxed code could trick trusted system modules into using attacker-created modules. For services that run user-submitted Racket, this could let a user influence restricted system functions. The vendor fixed the issue in Racket 8.2.

Executive priority

Treat this as moderate priority unless your organization runs untrusted Racket evaluation. For education, coding platform, or hosted evaluation environments, prioritize remediation because the issue crosses intended sandbox boundaries and affects integrity controls.

Technical view

CVE-2021-32773 is a CWE-441 confused deputy issue in Racket before 8.2. Sandbox evaluation could alter module resolution so system modules used attacker-controlled dependencies, potentially granting access to restricted facilities. CVSS is 6.1 with high integrity impact, changed scope, high attack complexity, and required user interaction.

Likely exposure

Exposure is most likely in systems that evaluate arbitrary or multi-user Racket code, including sandbox-backed education or submission services. Normal Racket deployments without untrusted sandbox evaluation appear less likely exposed based on the supplied sources.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation requires a vulnerable Racket version and a context where untrusted code is evaluated through the sandbox.

Researcher notes

Focus review on sandbox module resolution and trusted system module dependency loading. Evidence supports integrity impact, not confidentiality or availability impact. The supplied bundle names Racket before 8.2 as affected and Racket 8.2 as fixed; it does not provide broader product impact evidence.

Mitigation direction

  • Upgrade affected Racket installations to version 8.2 or later.
  • Review the GitHub advisory for the documented workaround and applicability.
  • For arbitrary evaluation services, add external sandboxing such as containers to limit impact.
  • For multi-user evaluation systems, prioritize upgrade; the advisory says no workaround is possible.

Validation and detection

  • Inventory Racket versions and flag any installation older than 8.2.
  • Identify services that evaluate untrusted or user-submitted Racket code.
  • Check for sandbox-based workflows, especially multi-user evaluation systems.
  • Confirm production and build environments use the fixed Racket release.
Prepared
Confidence
high
Sources
4

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-441: 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
cve · low confidence lookup

CVE-2021-32773 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
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

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

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
3Source 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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N1.64Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2021-32773Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
racketracket< 8.2Listed
Weakness

CWE details

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

CWE-441 · source CWE mapping

Unintended Proxy or Intermediary ('Confused Deputy')

Unintended Proxy or Intermediary ('Confused Deputy') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.