← Back
CVE-2025-5917
low
CVSS 2.8
Out-of-Bounds Write in libarchive (CVE-2025-5917)
Summary
out-of-bounds write in libarchive (CVE-2025-5917). Risk of unauthorized operations or information disclosure.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-5917** has been found in libarchive.
Risk of unauthorized operations or information disclosure. CVSS score: 2.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "libarchive CVE-2025-5917" on the vendor's site.
CVE-2025-5917 (libarchive) — CWE-787 / CVSS v3 2.8
Attack vector: local
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
**out-of-bounds write** (CWE-787) exists in libarchive.
📍 Affected scope
libarchive — .
🔥 Severity
Severity: Low (CVSS 2.8/10). Risk of unauthorized operations or information disclosure
🔧 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 'libarchive' .` 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 'libarchive' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `libarchive` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- issue [email protected]
- patch [email protected]
- patch [email protected]
- web [email protected]