← Back
CVE-2023-36807
Vulnerability in pypdf2 (CVE-2023-36807)
Summary
vulnerability in pypdf2 (CVE-2023-36807). Risk of unauthorized operations or information disclosure. Exploitable via ``PyPDF2``. Mitigation: upgrade to `2.10.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2023-36807** has been found in pypdf2.
Attackers can target a specific entry point like ``PyPDF2`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade pypdf2 to **2.10.6** or later.
If unsure, ask your IT team or search "pypdf2 CVE-2023-36807" on the vendor's site.
CVE-2023-36807 (pypdf2) — CWE-835 /
Attack vector: local / unauthenticated / no user interaction
Attack surface: `PyPDF2`
Patched: `2.10.6` — 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
**A vulnerability** (CWE-835) exists in pypdf2. Attackers reach the vulnerable code path via ``PyPDF2`` without authentication.
📍 Affected scope
pypdf2 — . Attack surface: `PyPDF2`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.10.6**.
🛡️ 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 'pypdf2' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pypdf2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pypdf2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pypdf2 to 2.10.6ステージング環境で 2.10.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
pypdf2
[{"type":"ECOSYSTEM","events":[{"introduced":"2.10.5"},{"fixed":"2.10.6"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2023-36807
- advisory https://github.com/advisories/GHSA-hm9v-vj3r-r55m
- package https://github.com/py-pdf/pypdf
- package https://pypi.org/project/pypdf2
- web https://github.com/py-pdf/pypdf/security/advisories/GHSA-hm9v-vj3r-r55m
- web https://github.com/py-pdf/pypdf/issues/1329
- web https://github.com/py-pdf/pypdf/pull/1331
- web https://github.com/py-pdf/pypdf/commit/e6531a25325e7e0174b6a1ba03b57320b5227f6b