Skip to content
Fencer Vulns
high 8.8

CVE-2018-4359 json

Multiple memory corruption issues were addressed with improved memory handling.

published 2019-04-03 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-16145

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

Summary

Multiple memory corruption issues were addressed with improved memory handling. This issue affected versions prior to iOS 12, tvOS 12, watchOS 5, Safari 12, iTunes 12.9 for Windows, iCloud for Windows 7.7.

Patch / fix

  • apple safari 12
  • apple icloud 7.7
  • apple itunes 12.9
  • apple iphone_os 12.0
  • apple tvos 12
  • apple watchos 5.0
  • webkit2gtk Debian 14, Debian 13, Debian 12 2.22.0-2

debian advisories DEBIAN-CVE-2018-4359

  • webkit2gtk Ubuntu 18.04 LTS 2.22.2-0ubuntu0.18.04.1

ubuntu advisories UBUNTU-CVE-2018-4359

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • 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

  • gtk3 openSUSE Tumbleweed 2.32.4-1.1
  • webkit2gtk3 openSUSE Leap 15.0 2.22.5-lp150.2.9.1

opensuse advisories openSUSE-SU-2024:11506-1openSUSE-SU-2019:0081-1

Exploit prediction

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

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