Skip to content
Fencer Intel
high 8.8

CVE-2018-4416 in the critical feed json

Multiple memory corruption issues were addressed with improved memory handling.

published 7y ago modified 4mo ago also EUVD-2018-16202

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
35.4%
EPSS 35.4% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

Multiple memory corruption issues were addressed with improved memory handling. This issue affected versions prior to iOS 12.1, tvOS 12.1, watchOS 5.1, Safari 12.0.1, iTunes 12.9.1, iCloud for Windows 7.8.

Patch / fix

  • apple safari 12.0.1
  • apple icloud 7.8
  • apple itunes 12.9.1
  • apple iphone_os 12.1
  • apple tvos 12.1
  • apple watchos 5.1
  • webkit2gtk Debian 14, Debian 13, Debian 12 2.22.1-1

debian advisories DEBIAN-CVE-2018-4416

  • webkit2gtk3 SLE Module for Desktop Applications 15, SLE Module for Basesystem 15 2.22.5-3.13.1
  • webkit2gtk3 SLES for SAP 12 SP4, SLES for SAP 12 SP3, SLES for SAP 12 SP2 +12 more 2.22.4-2.29.3

suse advisories SUSE-SU-2019:0092-1SUSE-SU-2019:0059-1

  • webkit2gtk3 openSUSE Leap 15.0 2.22.5-lp150.2.9.1

opensuse advisories openSUSE-SU-2019:0081-1

Is CVE-2018-4416 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-45910)
  2. Published

Exploit prediction

35.44% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-45910 WebKit JSC JIT - 'JSPropertyNameEnumerator' Type Confusion dos, 2018-11-29

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

  • n/a iOS, tvOS, watchOS, Safari, iTunes for Windows, iCloud for Windows

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel 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.