CVE-2023-41050

Information disclosure through Python's "format" functionality in Zope AccessControl

HIGH
7.7
CVSS Score
Published: September 6, 2023 at 05:58 PM UTC
Updated: June 17, 2026 at 06:20 AM UTC
3 products affected across 2 vendorsZopeAccesscontrolAccessControl

Using AccessControl by zopefoundation?

Get instant alerts when new vulnerabilities affect AccessControl - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.7
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

AccessControl provides a general security framework for use in Zope. Python's "format" functionality allows someone controlling the format string to "read" objects accessible (recursively) via attribute access and subscription from accessible objects. Those attribute accesses and subscriptions use Python's full blown `getattr` and `getitem`, not the policy restricted `AccessControl` variants `_getattr_` and `_getitem_`. This can lead to critical information disclosure. `AccessControl` already provides a safe variant for `str.format` and denies access to `string.Formatter`. However, `str.format_map` is still unsafe. Affected are all users who allow untrusted users to create `AccessControl` controlled Python code and execute it. A fix has been introduced in versions 4.4, 5.8 and 6.2. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.45.0 ≤ v < 5.86.0 ≤ v < 6.2
Affected range stops below 4.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
v < 4.8.95.0 ≤ v < 5.8.4
Affected range stops below 4.8.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.8.4, so it looks safe — our inference, not a vendor statement
v < 4.4v < 4.8.9v < 5.8v < 5.8.4v < 6.2
Affected range stops below 4.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.8.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.8.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-200

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card