Vulnerabilities > Apple > Iphone OS > 7.0
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2019-03-05 | CVE-2019-6208 | Improper Initialization vulnerability in Apple Iphone OS, mac OS X and TV OS A memory initialization issue was addressed with improved memory handling. | 4.3 |
2019-03-05 | CVE-2019-6205 | Out-of-bounds Write vulnerability in Apple Iphone OS, mac OS X and Tvos A memory corruption issue was addressed with improved lock state checking. | 6.8 |
2019-03-05 | CVE-2019-6202 | Out-of-bounds Read vulnerability in Apple Iphone OS, mac OS X and Watchos An out-of-bounds read was addressed with improved bounds checking. | 6.8 |
2019-03-05 | CVE-2019-6200 | Out-of-bounds Read vulnerability in Apple Iphone OS and mac OS X An out-of-bounds read was addressed with improved input validation. | 5.8 |
2019-03-04 | CVE-2019-6235 | Out-of-bounds Write vulnerability in Apple products A memory corruption issue was addressed with improved validation. | 7.5 |
2019-03-04 | CVE-2019-6206 | Information Exposure vulnerability in Apple Iphone OS An issue existed with autofill resuming after it was canceled. | 5.0 |
2019-02-18 | CVE-2019-8906 | Out-of-bounds Read vulnerability in multiple products do_core_note in readelf.c in libmagic.a in file 5.35 has an out-of-bounds read because memcpy is misused. | 3.6 |
2019-01-11 | CVE-2018-4404 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Apple Iphone OS In iOS before 11.4 and macOS High Sierra before 10.13.5, a memory corruption issue exists and was addressed with improved memory handling. | 7.8 |
2019-01-11 | CVE-2018-4330 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Apple Iphone OS In iOS before 11.4, a memory corruption issue exists and was addressed with improved memory handling. | 9.3 |
2019-01-11 | CVE-2018-4298 | Unspecified vulnerability in Apple products In macOS High Sierra before 10.13.3, Security Update 2018-001 Sierra, and Security Update 2018-001 El Capitan, a permissions issue existed in Remote Management. | 9.8 |