CVE-2019-8598 json
An input validation issue was addressed with improved input validation.
published 6y ago modified 4mo ago also EUVD-2019-17988
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.3%
- EPSS 10.3% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
An input validation issue was addressed with improved input validation. This issue is fixed in iOS 12.3, macOS Mojave 10.14.5, tvOS 12.3, watchOS 5.2.1, iTunes for Windows 12.9.5, iCloud for Windows 7.12. A malicious application may be able to read restricted memory.
Patch / fix
- Apple iOS iOS 12.3
- Apple macOS macOS Mojave 10.14.5
- Apple tvOS tvOS 12.3
- Apple watchOS watchOS 5.2.1
- Apple iTunes for Windows iTunes for Windows 12.9.5
- Apple iCloud for Windows iCloud for Windows 7.12
Is CVE-2019-8598 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 FencerExploit prediction
10.25% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- Apple iOS
- Apple macOS
- Apple tvOS
- Apple watchOS
- Apple iTunes for Windows
- Apple iCloud for Windows
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
support.apple.com
/HT210118
vendor-advisory
-
support.apple.com
/HT210119
vendor-advisory
-
support.apple.com
/HT210120
vendor-advisory
-
support.apple.com
/HT210124
vendor-advisory
-
support.apple.com
/HT210125
vendor-advisory
-
support.apple.com
/HT210212
vendor-advisory
-
support.apple.com
/HT210122
vendor-advisory
- research.checkpoint.com /2019/select-code_execution-from-using-sqlite/
Sources
- CVE List CVE-2019-8598
- NVD CVE-2019-8598
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.