Skip to content
Fencer Vulns
high 8.2

CVE-2018-4182 json

In macOS High Sierra before 10.13.5, an access issue was addressed with additional sandbox restrictions on CUPS.

published 2019-01-11 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-15968

cvss
8.2
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

In macOS High Sierra before 10.13.5, an access issue was addressed with additional sandbox restrictions on CUPS.

Patch / fix

  • apple mac_os_x 10.13.5
  • cups SLES for SAP 11 SP4, SLES 11 SP4, SLE Software Development Kit 11 SP4 1.3.9-8.46.56.3.1
  • cups SLE Module for Development Tools 15, SLE Module for Desktop Applications 15, SLE Module for Basesystem 15 2.2.7-3.3.1
  • cups SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 +1 more 1.7.5-20.14.1

suse advisories SUSE-SU-2018:2233-1SUSE-SU-2018:2172-1SUSE-SU-2018:2162-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-4182 updated cvss 7.0

cups: Sandbox bypass due to insecure error handling

  • Red Hat Enterprise Linux 5 cups Red Hat Enterprise Linux 6 cups, cups-lpd, cups-php, cups-libs Red Hat Enterprise Linux 7 cups, cups-lpd, cups-libs, cups-client, cups-ipptool, cups-filesystem Red Hat Enterprise Linux 8 cups, cups-lpd, cups-libs, cups-client, cups-ipptool, cups-filesystem Red Hat Virtualization 4 cups
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 8.2 CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.