Security readout for executives and security teams
Plain-English summary
CVE-2023-37271 is a sandbox escape in RestrictedPython. If an attacker can submit Python code into a RestrictedPython environment, they may break out of the intended restrictions and potentially run arbitrary code inside the Python interpreter. Default Zope/Plone deployments are unlikely to be exposed unless untrusted users can create or edit specific script/template objects.
Executive priority
Treat this as high priority where RestrictedPython executes user-supplied code. For standard Zope/Plone deployments without untrusted script authoring, urgency is lower but still warrants inventory and version validation because sandbox escapes can undermine application trust boundaries.
Technical view
RestrictedPython failed to restrict access to stack frames and their attributes. Because generators and generator expressions are allowed, malicious code could obtain a current frame and traverse beyond the RestrictedPython boundary. The issue affects versions before 6.1 and before 5.3, and is tracked as CWE-913 with CVSS 8.4.
Likely exposure
Exposure is limited to deployments that let untrusted users write Python code executed by RestrictedPython. For Zope and Plone, the cited advisory says risk requires non-default administrator configuration allowing untrusted creation or editing of Script (Python), DTML Method, DTML Document, or Zope Page Template objects.
Exploitation context
The CVE is not in CISA KEV in the supplied bundle, and no cited source states active exploitation. Exploitation requires low privileges but high complexity and access to submit code into the restricted environment.
Researcher notes
Focus triage on whether RestrictedPython is used as a security boundary for untrusted code. The advisory describes frame access through generators as the escape path, but this analysis intentionally omits reproduction details. Evidence supports fixed versions and affected ranges, but not active exploitation.
Mitigation direction
- Upgrade RestrictedPython to version 6.1 or 5.3 or later.
- Remove untrusted user access to RestrictedPython code-authoring features.
- Review Zope/Plone permissions for the listed script and template object types.
- Update dependency lockfiles, containers, and deployed runtimes consistently.
- Follow the GitHub advisory for any environment-specific guidance.
Validation and detection
- Check installed RestrictedPython versions in production and build artifacts.
- Identify applications or products embedding RestrictedPython.
- Confirm untrusted users cannot author code executed by RestrictedPython.
- Review Zope/Plone roles for the listed object creation and edit permissions.
- Verify the fixed version is loaded at runtime after deployment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-913: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-37271 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L1.86Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/zopefoundation/RestrictedPython/security/advisories/GHSA-wqc8-x2pr-7jqhCVE reference · x_refsource_CONFIRM
- https://github.com/zopefoundation/RestrictedPython/commit/c8eca66ae49081f0016d2e1f094c3d72095ef531CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Dynamically-Managed Code Resources
Improper Control of Dynamically-Managed Code Resources represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.