iTunes 12.11.4.15
iTunes 12.11.4.15, released August 4, 2021, fixes 347 CVEs in iTunes. 2 of them are being exploited (CVE-2019-8506); 2 on CISA KEV. Patch Radar priority: Patch now. The latest iTunes is 12.13.12.3, which also fixes every one of these CVEs.
Superseded. The latest iTunes is 12.13.12.3, which also fixes every CVE on this page. Install that instead.
Priority of the 347 CVEs
Applies to
| Product | Version |
|---|---|
| iTunes | 12.11.4.15 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Patch now | CVE-2019-8506 | Apple Multiple Products Type Confusion Vulnerability | 8.8 | 0.1616 | KEVExploited |
| Patch now | CVE-2020-27932 | Apple Multiple Products Type Confusion Vulnerability | 7.8 | 0.1034 | KEVExploited |
| Urgent | CVE-2019-8600 | iTunes: A memory corruption issue was addressed with improved input validation. | 9.8 | 0.2032 | None reported |
| Urgent | CVE-2020-3909 | iTunes: A buffer overflow was addressed with improved bounds checking. | 9.8 | 0.0304 | None reported |
| Urgent | CVE-2019-8746 | iTunes: An out-of-bounds read was addressed with improved input validation. | 9.8 | 0.0300 | None reported |
| Urgent | CVE-2019-6235 | iTunes: A memory corruption issue was addressed with improved validation. | 10.0 | 0.0210 | None reported |
| Urgent | CVE-2020-3911 | iTunes: A buffer overflow was addressed with improved bounds checking. | 9.8 | 0.0164 | None reported |
| Urgent | CVE-2020-3910 | iTunes: A buffer overflow was addressed with improved size validation. | 9.8 | 0.0164 | None reported |
| Urgent | CVE-2018-4147 | iTunes: In iCloud for Windows before 7.3, Safari before 11.0.3, iTunes before 12.7.3 for Windows, and iOS before… | 9.8 | 0.0154 | None reported |
| Urgent | CVE-2019-8749 | iTunes: Multiple memory corruption issues were addressed with improved input validation. | 9.8 | 0.0149 | None reported |
| Urgent | CVE-2019-8756 | iTunes: Multiple memory corruption issues were addressed with improved input validation. | 9.8 | 0.0149 | None reported |
| Urgent | CVE-2019-8562 | iTunes: A memory corruption issue was addressed with improved validation. | 9.6 | 0.0137 | None reported |
| High | CVE-2020-9850 | iTunes: A logic issue was addressed with improved restrictions. | 9.8 | 0.7740 | None reported |
| High | CVE-2018-4233 | iTunes: Improper Restriction of Operations within the Bounds of a Memory Buffer | 8.8 | 0.5382 | None reported |
| High | CVE-2018-4162 | iTunes: An issue was discovered in certain Apple products. | 8.8 | 0.3784 | None reported |
| High | CVE-2018-4416 | iTunes: Multiple memory corruption issues were addressed with improved memory handling. | 8.8 | 0.3544 | None reported |
| High | CVE-2019-8689 | iTunes: Multiple memory corruption issues were addressed with improved memory handling. | 8.8 | 0.1364 | None reported |
| High | CVE-2018-4121 | iTunes: An issue was discovered in certain Apple products. | 8.8 | 0.1310 | None reported |
| High | CVE-2018-4441 | iTunes: A memory corruption issue was addressed with improved memory handling. | 8.8 | 0.1271 | None reported |
| High | CVE-2018-4192 | iTunes: An issue was discovered in certain Apple products. | 7.5 | 0.1195 | None reported |
| High | CVE-2019-8518 | iTunes: Multiple memory corruption issues were addressed with improved memory handling. | 8.8 | 0.1119 | None reported |
| High | CVE-2019-8672 | iTunes: Multiple memory corruption issues were addressed with improved memory handling. | 8.8 | 0.1111 | None reported |
| High | CVE-2018-4222 | iTunes: An issue was discovered in certain Apple products. | 8.8 | 0.1070 | None reported |
| High | CVE-2018-4314 | iTunes: A use after free issue was addressed with improved memory management. | 8.8 | 0.1030 | None reported |
| High | CVE-2019-8577 | iTunes: An input validation issue was addressed with improved memory handling. | 7.8 | 0.1026 | None reported |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.