Skip to content
Fencer Intel
high 8.8

CVE-2018-4210 json

In iOS before 11.3, Safari before 11.1, tvOS before 11.3, watchOS before 4.3, iTunes before 12.7.4 for Windows, an array indexing issue exi…

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

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 83%
public exploits
0
none known

Summary

In iOS before 11.3, Safari before 11.1, tvOS before 11.3, watchOS before 4.3, iTunes before 12.7.4 for Windows, an array indexing issue existed in the handling of a function in javascript core. This issue was addressed with improved checks.

Patch / fix

  • apple safari 11.1
  • apple itunes 12.7.4
  • webkitgtk webkitgtk+ 2.22.0
  • apple iphone_os 11.3
  • apple tvos 11.3
  • apple watchos 4.3
  • webkit2gtk Debian 14, Debian 13, Debian 12 2.22.0-2

debian advisories DEBIAN-CVE-2018-4210

  • webkit2gtk Ubuntu 18.04 LTS 2.22.2-0ubuntu0.18.04.1

ubuntu advisories UBUNTU-CVE-2018-4210

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

  • webkit2gtk3 openSUSE Leap 15.0 2.22.5-lp150.2.9.1

opensuse advisories openSUSE-SU-2019:0081-1

Is CVE-2018-4210 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

Exploit prediction

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

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

Classification

Weakness
  • CWE-129 Improper Validation of Array Index

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.