# CVE-2018-16509: Code injection in n/a > Attackers can execute arbitrary code via crafted PostScript files due to improper privilege restoration checks in Ghostscript. - **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 5 Sep 2018 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2018-16509, GHSA-98rm-3v6h-p8j6, RHSA-2018:3760, UBUNTU-CVE-2018-16509 ## What is CVE-2018-16509? CVE-2018-16509 is a high-severity code injection vulnerability in Artifex Ghostscript, published on 5 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description An issue was discovered in Artifex Ghostscript before 9.24. Incorrect "restoration of privilege" checking during handling of /invalidaccess exceptions could be used by attackers able to supply crafted PostScript to execute code using the "pipe" instruction. ## Which versions are affected by CVE-2018-16509? It affects 8 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ghostscript` | Red Hat:enterprise_linux:6::client | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-doc` | Red Hat:enterprise_linux:6::client | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-gtk` | Red Hat:enterprise_linux:6::client | All versions | 0:8.70-24.el6_10.2 | | `ghostscript` | Red Hat:enterprise_linux:6::computenode | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-doc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-gtk` | Red Hat:enterprise_linux:6::computenode | All versions | 0:8.70-24.el6_10.2 | | `ghostscript` | Red Hat:enterprise_linux:6::server | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-doc` | Red Hat:enterprise_linux:6::server | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-gtk` | Red Hat:enterprise_linux:6::server | All versions | 0:8.70-24.el6_10.2 | | `ghostscript` | Red Hat:enterprise_linux:6::workstation | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-doc` | Red Hat:enterprise_linux:6::workstation | All versions | 0:8.70-24.el6_10.2 | | `ghostscript-gtk` | Red Hat:enterprise_linux:6::workstation | All versions | 0:8.70-24.el6_10.2 | Products: Artifex Ghostscript, Artifex Gpl Ghostscript, Canonical Ubuntu Linux, Debian Debian Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Workstation. ## How do I fix CVE-2018-16509? Upgrade to a fixed version. ## Is CVE-2018-16509 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-16509 exists. Public exploit code: - PoC + Docker Environment for Python PIL/Pillow Remote Shell Command Execution via Ghostscript CVE-2018-16509 (github_poc): https://github.com/farisv/PIL-RCE-Ghostscript-CVE-2018-16509 - CVE-2018-16509 (Ghostscript contains multiple -dSAFER sandbox bypass vulnerabilities) (github_poc): https://github.com/knqyf263/CVE-2018-16509 - CVE-2018-16509 Docker Playground - Ghostscript command execution (github_poc): https://github.com/rhpco/CVE-2018-16509 - Ghostscript Failed Restore Command Execution (metasploit) - Ghostscript - Failed Restore Command Execution (Metasploit) (exploitdb) - Ghostscript - Failed Restore Command Execution (Metasploit) (exploitdb) ## Other vulnerabilities in Artifex Ghostscript - [CVE-2017-8291](https://insights.sbomify.com/CVE-2017-8291/): Artifex Ghostscript Type Confusion (high 7.8, exploited in the wild) - [CVE-2021-3781](https://insights.sbomify.com/CVE-2021-3781/): Command injection in ghostscript (critical 9.9) - [CVE-2025-27831](https://insights.sbomify.com/CVE-2025-27831/): Memory corruption in n/a (critical 9.8) - [CVE-2025-27832](https://insights.sbomify.com/CVE-2025-27832/): Memory corruption in n/a (critical 9.8) - [CVE-2025-27836](https://insights.sbomify.com/CVE-2025-27836/): Memory corruption in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-16509 and fix it if it is affected. What it is: CVE-2018-16509 is a high-severity code injection vulnerability in Artifex Ghostscript, published on 5 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-16509 exists. Affected product: Artifex Ghostscript. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2018-16509/ (Markdown: https://insights.sbomify.com/CVE-2018-16509/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-16509 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-16509 - OSV: https://osv.dev/vulnerability/CVE-2018-16509 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-16509/ Summaries are generated and may contain mistakes; the official description above is the record.