Skip to content

try/except* clauses could allow bypass RestrictedPython via type confusion bug in the CPython interpreter

High severity GitHub Reviewed Published Jan 23, 2025 in zopefoundation/RestrictedPython • Updated Jan 23, 2025

Package

pip RestrictedPython (pip)

Affected versions

>= 6.0, < 8.0

Patched versions

8.0

Description

Impact

Via a type confusion bug in the CPython interpreter when using try/except* RestrictedPython could be bypassed.

We believe this should be fixed upstream in Python itself until that we remove support for try/except* from RestrictedPython.
(It has been fixed for some Python versions.)

Patches

Patched in version 8.0 by removing support for try/except* clauses

Workarounds

There is no workaround.

References

none

References

@icemac icemac published to zopefoundation/RestrictedPython Jan 23, 2025
Published to the GitHub Advisory Database Jan 23, 2025
Reviewed Jan 23, 2025
Published by the National Vulnerability Database Jan 23, 2025
Last updated Jan 23, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:L

EPSS score

Weaknesses

CVE ID

CVE-2025-22153

GHSA ID

GHSA-gmj9-h825-chq2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.