Categories
CVE-2023-6507 medium CVSS 6.1

Privilege Escalation in CPython (CVE-2023-6507)

Summary

Vulnerability in CPython (CVE-2023-6507). Confidential information can be exposed externally. Exploitable via subprocess.

Original description

The description as published by the source.

An issue was found in CPython 3.12.0 subprocess module on POSIX platforms. The issue was fixed in CPython 3.12.1 and does not affect other stable releases.

When using the extra_groups= parameter with an empty list as a value (ie extra_groups=[]) the logic regressed to not call setgroups(0, NULL) before calling exec(), thus not dropping the original processes' groups before starting the new process. There is no issue when the parameter isn't used or when any value is used besides an empty list.

This issue only impacts CPython processes run with sufficient privilege to make the setgroups system call (typically root).

Source: NIST National Vulnerability Database NVD GitHub Advisory

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-6507 has been found in CPython.
Attackers can target a specific entry point like subprocess over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CPython CVE-2023-6507" on the vendor's site.

CVE-2023-6507 (CPython) — CWE-269 / CVSS v3 6.1
Attack vector: adjacent-network / no user interaction
Attack surface: subprocess / setgroups / root
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 CPython. Attackers reach the vulnerable code path via subprocess.

📍 Affected scope

Check the vendor advisory for the affected versions of CPython. Attack surface: subprocess / setgroups / root.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 'CPython' . 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 'CPython' . | grep -v node_modules

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

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

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

Affected packages

Bitnami libpython
[{"type":"SEMVER","events":[{"introduced":"3.12.0"},{"fixed":"3.12.1"}]}]
Bitnami python-min
[{"type":"SEMVER","events":[{"introduced":"3.12.0"},{"fixed":"3.12.1"}]}]
Bitnami python
[{"type":"SEMVER","events":[{"introduced":"3.12.0"},{"fixed":"3.12.1"}]}]

References

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