Vulnerability in python-ldap (CVE-2021-46823)
Summary
Vulnerability in python-ldap (CVE-2021-46823). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.4.0 or later.
Original description
The description as published by the source.
python-ldap before 3.4.0 is vulnerable to a denial of service when ldap.schema is used for untrusted schema definitions, because of a regular expression denial of service (ReDoS) flaw in the LDAP schema parser. By sending crafted regex input, a remote authenticated attacker could exploit this vulnerability to cause a denial of service condition.
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-2021-46823 has been found in python-ldap.
Risk of unauthorized operations or information disclosure.
What to do: upgrade python-ldap to 3.4.0 or later.
If unsure, ask your IT team or search "python-ldap CVE-2021-46823" on the vendor's site.
CVE-2021-46823 (python-ldap) — CWE-1333
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.4.0 — 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.
A vulnerability (CWE-1333) exists in python-ldap.
Check the vendor advisory for the affected versions of python-ldap.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'python-ldap' . 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
-
1Identify exposure identify
grep -r 'python-ldap' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
python-ldapを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade python-ldap to 3.4.0ステージング環境で 3.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory exchange.xforce.ibmcloud.com
- package github.com
- web github.com