Path Traversal in SharpZipLib (CVE-2018-1002208)
Summary
Path traversal in SharpZipLib (CVE-2018-1002208). Data can be tampered with by attackers. Mitigation: upgrade to 1.0.0-rc1 or later.
Original description
The description as published by the source.
SharpZipLib before 1.0 RC1 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in a Zip archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'.
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-2018-1002208 has been found in SharpZipLib.
Data can be tampered with by attackers.
What to do: upgrade SharpZipLib to 1.0.0-rc1 or later.
If unsure, ask your IT team or search "SharpZipLib CVE-2018-1002208" on the vendor's site.
CVE-2018-1002208 (SharpZipLib) — CWE-22
Attack vector: local / unauthenticated
Patched: 1.0.0-rc1 — 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.
Path traversal (CWE-22) exists in SharpZipLib.
Check the vendor advisory for the affected versions of SharpZipLib.
Severity: ?. Data can be tampered with by attackers.
Update to 1.0.0-rc1.
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 'SharpZipLib' . 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 'SharpZipLib' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
SharpZipLibを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade SharpZipLib to 1.0.0-rc1ステージング環境で 1.0.0-rc1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory snyk.io
- patch github.com
- patch github.com
- patch snyk.io