CVE-2019-3839
CVE-2019-3839 Vulnerability Analysis & Exploit Intelligence
It was found that in ghostscript some privileged operators remained accessible from various places after the CVE-2019-6116 fix. A specially crafted PostScript file could use this flaw in order to, for example, have access to the file system outside of the constrains imposed by -dSAFER. Ghostscript versions before 9.27 are vulnerable.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
2%
chance of exploitation in 30 days
CVSS base
7.3
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.3 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-648
References
12 on the record
- access.redhat.com/errata/RHSA-2019:0971
vendor-advisory, x_refsource_REDHAT
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3839
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2019:1017
vendor-advisory, x_refsource_REDHAT
- usn.ubuntu.com/3970-1/
vendor-advisory, x_refsource_UBUNTU
- www.debian.org/security/2019/dsa-4442
vendor-advisory, x_refsource_DEBIAN
- seclists.org/bugtraq/2019/May/23
mailing-list, x_refsource_BUGTRAQ
- git.ghostscript.com/?p=ghostpdl.git%3Ba=commitdiff%3Bh=4ec9ca74bed49f2a82acb4bf430eae0d8b3b75c9
x_refsource_CONFIRM
- lists.debian.org/debian-lts-announce/2019/05/msg00023.html
mailing-list, x_refsource_MLIST
Elsewhere on this site
- the ghostscript projectevery CVE for this vendor
- CWE-648other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.