Vulnerabilities > Apple > Tvos > 11.4.1
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2019-04-03 | CVE-2018-4203 | Out-of-bounds Read vulnerability in Apple products An out-of-bounds read was addressed with improved bounds checking. | 5.0 |
| 2019-04-03 | CVE-2018-4197 | Use After Free vulnerability in Apple products A use after free issue was addressed with improved memory management. | 6.8 |
| 2019-04-03 | CVE-2018-4191 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Apple products A memory corruption issue was addressed with improved validation. | 6.8 |
| 2019-04-03 | CVE-2018-4126 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Apple products A memory corruption issue was addressed with improved memory handling. | 9.3 |
| 2019-04-03 | CVE-2018-20506 | Integer Overflow or Wraparound vulnerability in multiple products SQLite before 3.25.3, when the FTS3 extension is enabled, encounters an integer overflow (and resultant buffer overflow) for FTS3 queries in a "merge" operation that occurs after crafted changes to FTS3 shadow tables, allowing remote attackers to execute arbitrary code by leveraging the ability to run arbitrary SQL statements (such as in certain WebSQL use cases). | 6.8 |
| 2019-03-05 | CVE-2019-6234 | Out-of-bounds Write vulnerability in multiple products A memory corruption issue was addressed with improved memory handling. | 6.8 |
| 2019-03-05 | CVE-2019-6233 | Out-of-bounds Write vulnerability in Apple products A memory corruption issue was addressed with improved memory handling. | 6.8 |
| 2019-03-05 | CVE-2019-6231 | Out-of-bounds Read vulnerability in Apple products An out-of-bounds read was addressed with improved bounds checking. | 4.3 |
| 2019-03-05 | CVE-2019-6230 | Improper Initialization vulnerability in Apple products A memory initialization issue was addressed with improved memory handling. | 6.8 |
| 2019-03-05 | CVE-2019-6229 | Cross-site Scripting vulnerability in Apple products A logic issue was addressed with improved validation. | 4.3 |