LiveActive security incident?Get immediate response
CVE Record

CVE-2018-16585: An issue was discovered in Artifex Ghostscript before 9.24.

An issue was discovered in Artifex Ghostscript before 9.24. The .setdistillerkeys PostScript command is accepted even though it is not intended for use during document processing (e.g., after the startup phase). This leads to memory corruption, allowing remote attackers able to supply crafted PostScript to crash the interpreter or possibly have unspecified other impact. Note: A reputable source believes that the CVE is potentially a duplicate of CVE-2018-15910 as explained in Red Hat bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1626193)

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Ghostscript before 9.24 could mishandle a PostScript command that should not be accepted during normal document processing. A crafted PostScript file could crash the interpreter and may cause broader memory-corruption impact. The source record does not prove active exploitation or define the full impact. Exposure is most likely where Ghostscript processes untrusted PostScript or document-conversion input, such as upload, print, preview, or batch conversion workflows. The bundle does not identify specific downstream products beyond Ghostscript and vendor-packaged distributions. Prioritize remediation for systems that automatically process user-submitted documents. The likely business impact is service disruption, with possible but unspecified memory-corruption consequences. Systems without untrusted PostScript processing are lower urgency but still should update through normal patch cycles. Mitigation focus: Upgrade Ghostscript to vendor-fixed packages or 9.24 or later where applicable.; Review Gentoo, Ubuntu, Debian, and Red Hat guidance for distribution-specific fixes.; Limit Ghostscript processing of untrusted PostScript where operationally possible..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-16585 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.