HIGH · CVSS 7.8 CISA Known Exploited Vulnerability

CVE-2019-8605

Apple Multiple Products Use-After-Free Vulnerability

Apple Multiple Products

A use after free issue was addressed with improved memory management. This issue is fixed in iOS 12.3, macOS Mojave 10.14.5, tvOS 12.3, watchOS 5.2.1. A malicious application may be able to execute arbitrary code with system privileges.

CVSS
7.8
HIGH
EPSS
17.6%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
18 Dec 2019
CWE-416

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 27 June 2022. US federal agencies were required to remediate it by 18 July 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 17.6%, which is higher than 97.1% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2019-8605 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2019-8605.

What does CVE-2019-8605 affect?

CVE-2019-8605 affects Apple Multiple Products. A use after free issue was addressed with improved memory management. This issue is fixed in iOS 12.3, macOS Mojave 10.14.5, tvOS 12.3, watchOS 5.2.1. A malicious application may be able to execute arbitrary code with system privileges.

How severe is CVE-2019-8605?

CVE-2019-8605 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 17.6%, higher than 97.1% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 18 July 2022.

How should organisations respond to CVE-2019-8605?

Apply the vendor patch for Apple Multiple Products as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.