Use-After-Free in Artifex Ghostscript (CVE-2016-10217)
Summary
Vulnerability in Artifex Ghostscript (CVE-2016-10217). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
The pdf14_open function in base/gdevp14.c in Artifex Software, Inc. Ghostscript 9.20 allows remote attackers to cause a denial of service (use-after-free and application crash) via a crafted file that is mishandled in the color management module.
Source: NIST National Vulnerability Database NVD
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-2016-10217 has been found in Artifex Ghostscript.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Artifex Ghostscript CVE-2016-10217" on the vendor's site.
CVE-2016-10217 (Artifex Ghostscript) — CWE-416 / CVSS v3 5.5
Attack vector: local / unauthenticated
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.
Use-after-free (CWE-416) exists in Artifex Ghostscript.
Check the vendor advisory for the affected versions of Artifex Ghostscript.
Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
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 'Ghostscript' . 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 'Ghostscript' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Ghostscriptを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit bugs.ghostscript.com
- web git.ghostscript.com