CVE-2019-6236
CVE-2019-6236 is a high-severity vulnerability in Apple Icloud with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.
Key facts
- Severity: High (CVSS 3.x base score 7.5)
- CVSS v2: 7.6
- EPSS exploit prediction: 1% (64th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-362
- Affected product: Apple Icloud
- Published:
- Last modified:
Description
A race condition existed during the installation of iCloud for Windows. This was addressed with improved state handling. This issue is fixed in iCloud for Windows 7.11. Running the iCloud installer in an untrusted directory may result in arbitrary code execution.
Frequently asked questions
- What is CVE-2019-6236?
- A race condition existed during the installation of iCloud for Windows. This was addressed with improved state handling. This issue is fixed in iCloud for Windows 7.11. Running the iCloud installer in an untrusted directory may result in arbitrary code execution.
- How severe is CVE-2019-6236?
- CVE-2019-6236 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2019-6236 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (64th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2019-6236?
- CVE-2019-6236 affects Apple Icloud. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2019-6236?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2019-6236 published?
- CVE-2019-6236 was published on 2019-12-18 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:apple:icloud:*:*:*:*:*:windows:*:*
More vulnerabilities in Apple Icloud
- CVE-2019-8756 — Critical (CVSS 9.8): Multiple memory corruption issues were addressed with improved input validation. This issue is fixed in macOS Catalina…
- CVE-2019-8749 — Critical (CVSS 9.8): Multiple memory corruption issues were addressed with improved input validation. This issue is fixed in macOS Catalina…
- CVE-2019-8746 — Critical (CVSS 9.8): An out-of-bounds read was addressed with improved input validation. This issue is fixed in macOS Catalina 10.15, iOS…
- CVE-2020-9895 — Critical (CVSS 9.8): A use after free issue was addressed with improved memory management. This issue is fixed in iOS 13.6 and iPadOS 13.6,…
- CVE-2020-9850 — Critical (CVSS 9.8): A logic issue was addressed with improved restrictions. This issue is fixed in iOS 13.5 and iPadOS 13.5, tvOS 13.4.5,…
- CVE-2020-3911 — Critical (CVSS 9.8): A buffer overflow was addressed with improved bounds checking. This issue is fixed in iOS 13.4 and iPadOS 13.4, macOS…
All CVEs affecting Apple Icloud →
Other CWE-362 (Race Condition) vulnerabilities
- CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
- CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
- CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
- CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
- CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
- CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…