Categories
CVE-2023-41050

Information Disclosure in accesscontrol (CVE-2023-41050)

Summary

Vulnerability in accesscontrol (CVE-2023-41050). Confidential information can be exposed externally. Exploitable via getattr. Mitigation: upgrade to 6.2 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2023-41050 has been found in accesscontrol.
Attackers can target a specific entry point like getattr over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade accesscontrol to 6.2 or later.
If unsure, ask your IT team or search "accesscontrol CVE-2023-41050" on the vendor's site.

CVE-2023-41050 (accesscontrol) — CWE-200
Attack vector: remote (network-reachable) / no user interaction
Attack surface: getattr / getitem / AccessControl / _getattr_
Patched: 6.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in accesscontrol. Attackers reach the vulnerable code path via getattr.

📍 Affected scope

Check the vendor advisory for the affected versions of accesscontrol. Attack surface: getattr / getitem / AccessControl / _getattr_.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 6.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'accesscontrol' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'accesscontrol' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で accesscontrol を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade accesscontrol to 6.2

    ステージング環境で 6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI accesscontrol
[{"type":"ECOSYSTEM","events":[{"introduced":"6.0"},{"fixed":"6.2"}]}]
PyPI zope
[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"fixed":"5.8.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details