Categories
CVE-2024-51734

Privilege Escalation in accesscontrol (CVE-2024-51734)

Summary

Vulnerability in accesscontrol (CVE-2024-51734). Data can be tampered with by attackers. Exploitable via AccessControl.userfolder.UserFolder. Mitigation: upgrade to 7.2 or later.

Original description

The description as published by the source.

Impact

Anonymous users can delete the user data maintained by an AccessControl.userfolder.UserFolder which may prevent any privileged access.

Patches

The problem is fixed in version 7.2.

Workarounds

The problem can be fixed by adding data__roles__ = () to AccessControl.userfolder.UserFolder.

References

https://github.com/zopefoundation/AccessControl/issues/159

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-2024-51734 has been found in accesscontrol.
Attackers can target a specific entry point like AccessControl.userfolder.UserFolder over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade accesscontrol to 7.2 or later.
If unsure, ask your IT team or search "accesscontrol CVE-2024-51734" on the vendor's site.

CVE-2024-51734 (accesscontrol) — CWE-269
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: AccessControl.userfolder.UserFolder
Patched: 7.2 — apply immediately
Workaround: The problem can be fixed by adding data__roles__ = () to AccessControl.userfolder.UserFolder.
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

A vulnerability (CWE-269) exists in accesscontrol. Attackers reach the vulnerable code path via AccessControl.userfolder.UserFolder without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of accesscontrol. Attack surface: AccessControl.userfolder.UserFolder.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 7.2.

🛡️ Workaround

Workaround: The problem can be fixed by adding data__roles__ = () to AccessControl.userfolder.UserFolder.

🔍 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 temporary workaround mitigate
    The problem can be fixed by adding `data__roles__ = ()` to `AccessControl.userfolder.UserFolder`.

    パッチが適用されるまでの応急処置として、The problem can be fixed by adding data__roles__ = () to AccessControl.userfolder.UserFolder. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade accesscontrol to 7.2

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

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

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

Affected packages

PyPI accesscontrol
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2"}]}]
PyPI zope
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.11.1"}]}]

References

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