| Bug | Description |
|---|
| CVE-2025-31257 | This issue was addressed with improved memory handling. This issue is ... |
| CVE-2025-31215 | The issue was addressed with improved checks. This issue is fixed in w ... |
| CVE-2025-31206 | A type confusion issue was addressed with improved state handling. Thi ... |
| CVE-2025-31205 | The issue was addressed with improved checks. This issue is fixed in w ... |
| CVE-2025-31204 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2025-30427 | A use-after-free issue was addressed with improved memory management. ... |
| CVE-2025-24264 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2025-24223 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2025-24216 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2025-24213 | This issue was addressed with improved handling of floats. This issue ... |
| CVE-2025-24209 | A buffer overflow issue was addressed with improved memory handling. T ... |
| CVE-2025-24208 | A permissions issue was addressed with additional restrictions. This i ... |
| CVE-2025-24201 | An out-of-bounds write issue was addressed with improved checks to pre ... |
| CVE-2025-24162 | This issue was addressed through improved state management. This issue ... |
| CVE-2025-24158 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2025-24150 | A privacy issue was addressed with improved handling of files. This is ... |
| CVE-2025-24143 | The issue was addressed with improved access restrictions to the file ... |
| CVE-2024-54658 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2024-54551 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2024-54543 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2024-54534 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2024-54508 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2024-54505 | A type confusion issue was addressed with improved memory handling. Th ... |
| CVE-2024-54502 | The issue was addressed with improved checks. This issue is fixed in w ... |
| CVE-2024-54479 | The issue was addressed with improved checks. This issue is fixed in i ... |
| CVE-2024-54467 | A cookie management issue was addressed with improved state management ... |
| CVE-2024-44309 | A cookie management issue was addressed with improved state management ... |
| CVE-2024-44308 | The issue was addressed with improved checks. This issue is fixed in S ... |
| CVE-2024-44296 | The issue was addressed with improved checks. This issue is fixed in t ... |
| CVE-2024-44244 | A memory corruption issue was addressed with improved input validation ... |
| CVE-2024-44192 | The issue was addressed with improved checks. This issue is fixed in w ... |
| CVE-2024-44187 | A cross-origin issue existed with "iframe" elements. This was addresse ... |
| CVE-2024-44185 | The issue was addressed with improved checks. This issue is fixed in t ... |
| CVE-2024-40866 | The issue was addressed with improved UI. This issue is fixed in Safar ... |
| CVE-2024-40794 | This issue was addressed through improved state management. This issue ... |
| CVE-2024-40789 | An out-of-bounds access issue was addressed with improved bounds check ... |
| CVE-2024-40785 | This issue was addressed with improved checks. This issue is fixed in ... |
| CVE-2024-40782 | A use-after-free issue was addressed with improved memory management. ... |
| CVE-2024-40780 | An out-of-bounds read was addressed with improved bounds checking. Thi ... |
| CVE-2024-40779 | An out-of-bounds read was addressed with improved bounds checking. Thi ... |
| CVE-2024-40776 | A use-after-free issue was addressed with improved memory management. ... |
| CVE-2024-27856 | The issue was addressed with improved checks. This issue is fixed in m ... |
| CVE-2024-27851 | The issue was addressed with improved bounds checks. This issue is fix ... |
| CVE-2024-27838 | The issue was addressed by adding additional logic. This issue is fixe ... |
| CVE-2024-27834 | The issue was addressed with improved checks. This issue is fixed in i ... |
| CVE-2024-27833 | An integer overflow was addressed with improved input validation. This ... |
| CVE-2024-27820 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2024-27808 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2024-23284 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2024-23280 | An injection issue was addressed with improved validation. This issue ... |
| CVE-2024-23271 | A logic issue was addressed with improved checks. This issue is fixed ... |
| CVE-2024-23263 | A logic issue was addressed with improved validation. This issue is fi ... |
| CVE-2024-23254 | The issue was addressed with improved UI handling. This issue is fixed ... |
| CVE-2024-23222 | A type confusion issue was addressed with improved checks. This issue ... |
| CVE-2024-23213 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2024-23206 | An access issue was addressed with improved access restrictions. This ... |
| CVE-2024-4558 | Use after free in ANGLE in Google Chrome prior to 124.0.6367.155 allow ... |
| CVE-2023-42970 | A use-after-free issue was addressed with improved memory management. ... |
| CVE-2023-42956 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2023-42950 | A use after free issue was addressed with improved memory management. ... |
| CVE-2023-42917 | A memory corruption vulnerability was addressed with improved locking. ... |
| CVE-2023-42916 | An out-of-bounds read was addressed with improved input validation. Th ... |
| CVE-2023-42890 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2023-42883 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2023-42875 | Processing web content may lead to arbitrary code execution. This issu ... |
| CVE-2023-42852 | A logic issue was addressed with improved checks. This issue is fixed ... |
| CVE-2023-42843 | An inconsistent user interface issue was addressed with improved state ... |
| CVE-2023-42833 | A correctness issue was addressed with improved checks. This issue is ... |
| CVE-2023-41993 | The issue was addressed with improved checks. This issue is fixed in m ... |
| CVE-2023-41983 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2023-41074 | The issue was addressed with improved checks. This issue is fixed in t ... |
| CVE-2023-40451 | This issue was addressed with improved iframe sandbox enforcement. Thi ... |
| CVE-2023-40414 | A use-after-free issue was addressed with improved memory management. ... |
| CVE-2023-40397 | The issue was addressed with improved checks. This issue is fixed in m ... |
| CVE-2023-39928 | A use-after-free vulnerability exists in the MediaRecorder API of Webk ... |
| CVE-2023-39434 | A use-after-free issue was addressed with improved memory management. ... |
| CVE-2023-38611 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2023-38600 | The issue was addressed with improved checks. This issue is fixed in i ... |
| CVE-2023-38599 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2023-38597 | The issue was addressed with improved checks. This issue is fixed in i ... |
| CVE-2023-38595 | The issue was addressed with improved checks. This issue is fixed in i ... |
| CVE-2023-38594 | The issue was addressed with improved checks. This issue is fixed in i ... |
| CVE-2023-38592 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2023-38572 | The issue was addressed with improved checks. This issue is fixed in i ... |
| CVE-2023-38133 | The issue was addressed with improved checks. This issue is fixed in i ... |
| CVE-2023-37450 | The issue was addressed with improved checks. This issue is fixed in i ... |
| CVE-2023-35074 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2023-32439 | A type confusion issue was addressed with improved checks. This issue ... |
| CVE-2023-32435 | A memory corruption issue was addressed with improved state management ... |
| CVE-2023-32409 | The issue was addressed with improved bounds checks. This issue is fix ... |
| CVE-2023-32393 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2023-32373 | A use-after-free issue was addressed with improved memory management. ... |
| CVE-2023-32370 | A logic issue was addressed with improved validation. This issue is fi ... |
| CVE-2023-32359 | This issue was addressed with improved redaction of sensitive informat ... |
| CVE-2023-28205 | A use after free issue was addressed with improved memory management. ... |
| CVE-2023-28204 | An out-of-bounds read was addressed with improved input validation. Th ... |
| CVE-2023-28198 | A use-after-free issue was addressed with improved memory management. ... |
| CVE-2023-27954 | The issue was addressed by removing origin information. This issue is ... |
| CVE-2023-27932 | This issue was addressed with improved state management. This issue is ... |
| CVE-2023-25363 | A use-after-free vulnerability in WebCore::RenderLayer::updateDescenda ... |
| CVE-2023-25362 | A use-after-free vulnerability in WebCore::RenderLayer::repaintBlockSe ... |
| CVE-2023-25361 | A use-after-free vulnerability in WebCore::RenderLayer::setNextSibling ... |
| CVE-2023-25360 | A use-after-free vulnerability in WebCore::RenderLayer::renderer in We ... |
| CVE-2023-25358 | A use-after-free vulnerability in WebCore::RenderLayer::addChild in We ... |
| CVE-2023-23529 | A type confusion issue was addressed with improved checks. This issue ... |
| CVE-2023-23518 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2023-23517 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2023-2203 | A flaw was found in the WebKitGTK package. An improper input validatio ... |
| CVE-2022-48503 | The issue was addressed with improved bounds checks. This issue is fix ... |
| CVE-2022-46725 | A spoofing issue existed in the handling of URLs. This issue was addre ... |
| CVE-2022-46705 | A spoofing issue existed in the handling of URLs. This issue was addre ... |
| CVE-2022-46700 | A memory corruption issue was addressed with improved input validation ... |
| CVE-2022-46699 | A memory corruption issue was addressed with improved state management ... |
| CVE-2022-46698 | A logic issue was addressed with improved checks. This issue is fixed ... |
| CVE-2022-46692 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2022-46691 | A memory consumption issue was addressed with improved memory handling ... |
| CVE-2022-42867 | A use after free issue was addressed with improved memory management. ... |
| CVE-2022-42863 | A memory corruption issue was addressed with improved state management ... |
| CVE-2022-42856 | A type confusion issue was addressed with improved state handling. Thi ... |
| CVE-2022-42852 | The issue was addressed with improved memory handling. This issue is f ... |
| CVE-2022-42826 | A use after free issue was addressed with improved memory management. ... |
| CVE-2022-42824 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2022-42823 | A type confusion issue was addressed with improved memory handling. Th ... |
| CVE-2022-42799 | The issue was addressed with improved UI handling. This issue is fixed ... |
| CVE-2022-32933 | An information disclosure issue was addressed by removing the vulnerab ... |
| CVE-2022-32923 | A correctness issue in the JIT was addressed with improved checks. Thi ... |
| CVE-2022-32919 | The issue was addressed with improved UI handling. This issue is fixed ... |
| CVE-2022-32912 | An out-of-bounds read was addressed with improved bounds checking. Thi ... |
| CVE-2022-32893 | An out-of-bounds write issue was addressed with improved bounds checki ... |
| CVE-2022-32891 | The issue was addressed with improved UI handling. This issue is fixed ... |
| CVE-2022-32888 | An out-of-bounds write issue was addressed with improved bounds checki ... |
| CVE-2022-32886 | A buffer overflow issue was addressed with improved memory handling. T ... |
| CVE-2022-32885 | A memory corruption issue was addressed with improved validation. This ... |
| CVE-2022-32816 | The issue was addressed with improved UI handling. This issue is fixed ... |
| CVE-2022-32792 | An out-of-bounds write issue was addressed with improved input validat ... |
| CVE-2022-30293 | In WebKitGTK through 2.36.0 (and WPE WebKit), there is a heap-based bu ... |
| CVE-2022-26719 | A memory corruption issue was addressed with improved state management ... |
| CVE-2022-26717 | A use after free issue was addressed with improved memory management. ... |
| CVE-2022-26716 | A memory corruption issue was addressed with improved state management ... |
| CVE-2022-26710 | A use after free issue was addressed with improved memory management. ... |
| CVE-2022-26709 | A use after free issue was addressed with improved memory management. ... |
| CVE-2022-26700 | A memory corruption issue was addressed with improved state management ... |
| CVE-2022-22677 | A logic issue in the handling of concurrent media was addressed with i ... |
| CVE-2022-22662 | A cookie management issue was addressed with improved state management ... |
| CVE-2022-22637 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2022-22629 | A buffer overflow issue was addressed with improved memory handling. T ... |
| CVE-2022-22628 | A use after free issue was addressed with improved memory management. ... |
| CVE-2022-22624 | A use after free issue was addressed with improved memory management. ... |
| CVE-2022-22620 | A use after free issue was addressed with improved memory management. ... |
| CVE-2022-22594 | A cross-origin issue in the IndexDB API was addressed with improved in ... |
| CVE-2022-22592 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2022-22590 | A use after free issue was addressed with improved memory management. ... |
| CVE-2022-22589 | A validation issue was addressed with improved input sanitization. Thi ... |
| CVE-2022-2294 | Heap buffer overflow in WebRTC in Google Chrome prior to 103.0.5060.11 ... |
| CVE-2022-0108 | Inappropriate implementation in Navigation in Google Chrome prior to 9 ... |
| CVE-2021-45483 | In WebKitGTK before 2.32.4, there is a use-after-free in WebCore::Fram ... |
| CVE-2021-45482 | In WebKitGTK before 2.32.4, there is a use-after-free in WebCore::Cont ... |
| CVE-2021-45481 | In WebKitGTK before 2.32.4, there is incorrect memory allocation in We ... |
| CVE-2021-42762 | BubblewrapLauncher.cpp in WebKitGTK and WPE WebKit before 2.34.1 allow ... |
| CVE-2021-30984 | A race condition was addressed with improved state handling. This issu ... |
| CVE-2021-30954 | A type confusion issue was addressed with improved memory handling. Th ... |
| CVE-2021-30953 | An out-of-bounds read was addressed with improved bounds checking. Thi ... |
| CVE-2021-30952 | An integer overflow was addressed with improved input validation. This ... |
| CVE-2021-30951 | A use after free issue was addressed with improved memory management. ... |
| CVE-2021-30936 | A use after free issue was addressed with improved memory management. ... |
| CVE-2021-30934 | A buffer overflow issue was addressed with improved memory handling. T ... |
| CVE-2021-30890 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2021-30889 | A buffer overflow issue was addressed with improved memory handling. T ... |
| CVE-2021-30888 | An information leakage issue was addressed. This issue is fixed in iOS ... |
| CVE-2021-30887 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2021-30884 | The issue was resolved with additional restrictions on CSS compositing ... |
| CVE-2021-30858 | A use after free issue was addressed with improved memory management. ... |
| CVE-2021-30851 | A memory corruption vulnerability was addressed with improved locking. ... |
| CVE-2021-30849 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2021-30848 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2021-30846 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2021-30836 | An out-of-bounds read was addressed with improved input validation. Th ... |
| CVE-2021-30823 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2021-30818 | A type confusion issue was addressed with improved state handling. Thi ... |
| CVE-2021-30809 | A use after free issue was addressed with improved memory management. ... |
| CVE-2021-30799 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2021-30797 | This issue was addressed with improved checks. This issue is fixed in ... |
| CVE-2021-30795 | A use after free issue was addressed with improved memory management. ... |
| CVE-2021-30762 | A use after free issue was addressed with improved memory management. ... |
| CVE-2021-30761 | A memory corruption issue was addressed with improved state management ... |
| CVE-2021-30758 | A type confusion issue was addressed with improved state handling. Thi ... |
| CVE-2021-30749 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2021-30744 | Description: A cross-origin issue with iframe elements was addressed w ... |
| CVE-2021-30734 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2021-30720 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2021-30689 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2021-30682 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2021-30666 | A buffer overflow issue was addressed with improved memory handling. T ... |
| CVE-2021-30665 | A memory corruption issue was addressed with improved state management ... |
| CVE-2021-30663 | An integer overflow was addressed with improved input validation. This ... |
| CVE-2021-30661 | A use after free issue was addressed with improved memory management. ... |
| CVE-2021-21806 | An exploitable use-after-free vulnerability exists in WebKitGTK browse ... |
| CVE-2021-21779 | A use-after-free vulnerability exists in the way Webkit\u2019s Graphic ... |
| CVE-2021-21775 | A use-after-free vulnerability exists in the way certain events are pr ... |
| CVE-2021-1871 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2021-1870 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2021-1844 | A memory corruption issue was addressed with improved validation. This ... |
| CVE-2021-1826 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2021-1825 | An input validation issue was addressed with improved input validation ... |
| CVE-2021-1820 | A memory initialization issue was addressed with improved memory handl ... |
| CVE-2021-1817 | A memory corruption issue was addressed with improved state management ... |
| CVE-2021-1801 | This issue was addressed with improved iframe sandbox enforcement. Thi ... |
| CVE-2021-1799 | A port redirection issue was addressed with additional port validation ... |
| CVE-2021-1789 | A type confusion issue was addressed with improved state handling. Thi ... |
| CVE-2021-1788 | A use after free issue was addressed with improved memory management. ... |
| CVE-2021-1765 | This issue was addressed with improved iframe sandbox enforcement. Thi ... |
| CVE-2020-29623 | "Clear History and Website Data" did not clear the history. The issue ... |
| CVE-2020-27918 | A use after free issue was addressed with improved memory management. ... |
| CVE-2020-13753 | The bubblewrap sandbox of WebKitGTK and WPE WebKit, prior to 2.28.3, f ... |
| CVE-2020-13584 | An exploitable use-after-free vulnerability exists in WebKitGTK browse ... |
| CVE-2020-13558 | A code execution vulnerability exists in the AudioSourceProviderGStrea ... |
| CVE-2020-13543 | A code execution vulnerability exists in the WebSocket functionality o ... |
| CVE-2020-11793 | A use-after-free issue exists in WebKitGTK before 2.28.1 and WPE WebKi ... |
| CVE-2020-10018 | WebKitGTK through 2.26.4 and WPE WebKit through 2.26.4 (which are the ... |
| CVE-2020-9983 | An out-of-bounds write issue was addressed with improved bounds checki ... |
| CVE-2020-9952 | An input validation issue was addressed with improved input validation ... |
| CVE-2020-9951 | A use after free issue was addressed with improved memory management. ... |
| CVE-2020-9948 | A type confusion issue was addressed with improved memory handling. Th ... |
| CVE-2020-9947 | A use after free issue was addressed with improved memory management. ... |
| CVE-2020-9925 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2020-9915 | An access issue existed in Content Security Policy. This issue was add ... |
| CVE-2020-9895 | A use after free issue was addressed with improved memory management. ... |
| CVE-2020-9894 | An out-of-bounds read was addressed with improved input validation. Th ... |
| CVE-2020-9893 | A use after free issue was addressed with improved memory management. ... |
| CVE-2020-9862 | A command injection issue existed in Web Inspector. This issue was add ... |
| CVE-2020-9850 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2020-9843 | An input validation issue was addressed with improved input validation ... |
| CVE-2020-9807 | A memory corruption issue was addressed with improved state management ... |
| CVE-2020-9806 | A memory corruption issue was addressed with improved state management ... |
| CVE-2020-9805 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2020-9803 | A memory corruption issue was addressed with improved validation. This ... |
| CVE-2020-9802 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2020-3902 | An input validation issue was addressed with improved input validation ... |
| CVE-2020-3901 | A type confusion issue was addressed with improved memory handling. Th ... |
| CVE-2020-3900 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2020-3899 | A memory consumption issue was addressed with improved memory handling ... |
| CVE-2020-3897 | A type confusion issue was addressed with improved memory handling. Th ... |
| CVE-2020-3895 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2020-3894 | A race condition was addressed with additional validation. This issue ... |
| CVE-2020-3885 | A logic issue was addressed with improved restrictions. This issue is ... |
| CVE-2020-3868 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2020-3867 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2020-3865 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2020-3864 | A logic issue was addressed with improved validation. This issue is fi ... |
| CVE-2020-3862 | A denial of service issue was addressed with improved memory handling. ... |
| CVE-2019-11070 | WebKitGTK and WPE WebKit prior to version 2.24.1 failed to properly ap ... |
| CVE-2019-8846 | A use after free issue was addressed with improved memory management. ... |
| CVE-2019-8844 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8835 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8823 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8822 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8821 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8820 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8819 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8816 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8815 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8814 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8813 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2019-8812 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8811 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8808 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8783 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8782 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8771 | This issue was addressed with improved iframe sandbox enforcement. Thi ... |
| CVE-2019-8769 | An issue existed in the drawing of web page elements. The issue was ad ... |
| CVE-2019-8768 | "Clear History and Website Data" did not clear the history. The issue ... |
| CVE-2019-8766 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8765 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8764 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2019-8763 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8743 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8735 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8733 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8726 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8720 | A vulnerability was found in WebKit. The flaw is triggered when proces ... |
| CVE-2019-8719 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2019-8710 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8707 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8690 | A logic issue existed in the handling of document loads. This issue wa ... |
| CVE-2019-8689 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8688 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8687 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8686 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8684 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8683 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8681 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8680 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8679 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8678 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8677 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8676 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8674 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2019-8673 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8672 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8671 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8669 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8666 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8658 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2019-8649 | A logic issue existed in the handling of synchronous page loads. This ... |
| CVE-2019-8644 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8625 | A logic issue was addressed with improved state management. This issue ... |
| CVE-2019-8623 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8622 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8619 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8615 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8611 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8610 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8609 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8608 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8607 | An out-of-bounds read was addressed with improved input validation. Th ... |
| CVE-2019-8601 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8597 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8596 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8595 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8594 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8587 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8586 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8584 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8583 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8571 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8563 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8559 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8558 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8551 | A logic issue was addressed with improved validation. This issue is fi ... |
| CVE-2019-8544 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2019-8536 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2019-8535 | A memory corruption issue was addressed with improved state management ... |
| CVE-2019-8524 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8523 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8518 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-8515 | A cross-origin issue existed with the fetch API. This was addressed wi ... |
| CVE-2019-8506 | A type confusion issue was addressed with improved memory handling. Th ... |
| CVE-2019-8503 | A logic issue was addressed with improved validation. This issue is fi ... |
| CVE-2019-8375 | The UIProcess subsystem in WebKit, as used in WebKitGTK through 2.23.9 ... |
| CVE-2019-7292 | A validation issue was addressed with improved logic. This issue is fi ... |
| CVE-2019-7285 | A use after free issue was addressed with improved memory management. ... |
| CVE-2019-6251 | WebKitGTK and WPE WebKit prior to version 2.24.1 are vulnerable to add ... |
| CVE-2019-6237 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-6234 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2019-6233 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2019-6229 | A logic issue was addressed with improved validation. This issue is fi ... |
| CVE-2019-6227 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2019-6226 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-6217 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-6216 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-6215 | A type confusion issue was addressed with improved memory handling. Th ... |
| CVE-2019-6212 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2019-6201 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-12911 | WebKitGTK+ 2.20.3 has an off-by-one error, with a resultant out-of-bou ... |
| CVE-2018-12294 | WebCore/platform/graphics/texmap/TextureMapperLayer.cpp in WebKit, as ... |
| CVE-2018-12293 | The getImageData function in the ImageBufferCairo class in WebCore/pla ... |
| CVE-2018-11713 | WebCore/platform/network/soup/SocketStreamHandleImplSoup.cpp in the li ... |
| CVE-2018-11712 | WebCore/platform/network/soup/SocketStreamHandleImplSoup.cpp in the li ... |
| CVE-2018-11646 | webkitFaviconDatabaseSetIconForPageURL and webkitFaviconDatabaseSetIco ... |
| CVE-2018-4464 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4443 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2018-4442 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2018-4441 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2018-4438 | A logic issue existed resulting in memory corruption. This was address ... |
| CVE-2018-4437 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4416 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4392 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4386 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4382 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4378 | A memory corruption issue was addressed with improved validation. This ... |
| CVE-2018-4376 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4375 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4373 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4372 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4361 | A memory consumption issue was addressed with improved memory handling ... |
| CVE-2018-4359 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4358 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4345 | A cross-site scripting issue existed in Safari. This issue was address ... |
| CVE-2018-4328 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4323 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4319 | A cross-origin issue existed with "iframe" elements. This was addresse ... |
| CVE-2018-4318 | A use after free issue was addressed with improved memory management. ... |
| CVE-2018-4317 | A use after free issue was addressed with improved memory management. ... |
| CVE-2018-4316 | A memory corruption issue was addressed with improved state management ... |
| CVE-2018-4315 | A use after free issue was addressed with improved memory management. ... |
| CVE-2018-4314 | A use after free issue was addressed with improved memory management. ... |
| CVE-2018-4312 | A use after free issue was addressed with improved memory management. ... |
| CVE-2018-4311 | The issue was addressed by removing origin information. This issue aff ... |
| CVE-2018-4309 | A cross-site scripting issue existed in Safari. This issue was address ... |
| CVE-2018-4306 | A use after free issue was addressed with improved memory management. ... |
| CVE-2018-4299 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4284 | A type confusion issue was addressed with improved memory handling. Th ... |
| CVE-2018-4278 | In Safari before 11.1.2, iTunes before 12.8 for Windows, iOS before 11 ... |
| CVE-2018-4273 | Multiple memory corruption issues were addressed with improved input v ... |
| CVE-2018-4272 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4271 | Multiple memory corruption issues were addressed with improved input v ... |
| CVE-2018-4270 | A memory corruption issue was addressed with improved memory handling. ... |
| CVE-2018-4267 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4266 | A race condition was addressed with additional validation. This issue ... |
| CVE-2018-4265 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4264 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4263 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4262 | In Safari before 11.1.2, iTunes before 12.8 for Windows, iOS before 11 ... |
| CVE-2018-4261 | Multiple memory corruption issues were addressed with improved memory ... |
| CVE-2018-4246 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4233 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4232 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4222 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4218 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4214 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4213 | In iOS before 11.3, Safari before 11.1, iCloud for Windows before 7.4, ... |
| CVE-2018-4212 | In iOS before 11.3, Safari before 11.1, iCloud for Windows before 7.4, ... |
| CVE-2018-4210 | In iOS before 11.3, Safari before 11.1, tvOS before 11.3, watchOS befo ... |
| CVE-2018-4209 | In iOS before 11.3, Safari before 11.1, iCloud for Windows before 7.4, ... |
| CVE-2018-4208 | In iOS before 11.3, Safari before 11.1, iCloud for Windows before 7.4, ... |
| CVE-2018-4207 | In iOS before 11.3, Safari before 11.1, iCloud for Windows before 7.4, ... |
| CVE-2018-4204 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4201 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4200 | An issue was discovered in certain Apple products. iOS before 11.3.1 i ... |
| CVE-2018-4199 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4197 | A use after free issue was addressed with improved memory management. ... |
| CVE-2018-4192 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4191 | A memory corruption issue was addressed with improved validation. This ... |
| CVE-2018-4190 | An issue was discovered in certain Apple products. iOS before 11.4 is ... |
| CVE-2018-4165 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4163 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4162 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4161 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4146 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4133 | An issue was discovered in certain Apple products. Safari before 11.1 ... |
| CVE-2018-4129 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4128 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4127 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4125 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4122 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4121 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4120 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4119 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4118 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4117 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4114 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4113 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4101 | An issue was discovered in certain Apple products. iOS before 11.3 is ... |
| CVE-2018-4096 | An issue was discovered in certain Apple products. iOS before 11.2.5 i ... |
| CVE-2018-4089 | An issue was discovered in certain Apple products. iOS before 11.2.5 i ... |
| CVE-2018-4088 | An issue was discovered in certain Apple products. iOS before 11.2.5 i ... |
| CVE-2017-1000122 | The UNIX IPC layer in WebKit, including WebKitGTK+ prior to 2.16.3, do ... |
| CVE-2017-1000121 | The UNIX IPC layer in WebKit, including WebKitGTK+ prior to 2.16.3, do ... |
| CVE-2017-17821 | WTF/wtf/FastBitVector.h in WebKit, as distributed in Safari Technology ... |
| CVE-2017-13885 | An issue was discovered in certain Apple products. iOS before 11.2 is ... |
| CVE-2017-13884 | An issue was discovered in certain Apple products. iOS before 11.2 is ... |
| CVE-2017-13870 | An issue was discovered in certain Apple products. iOS before 11.2 is ... |
| CVE-2017-13866 | An issue was discovered in certain Apple products. iOS before 11.2 is ... |
| CVE-2017-13856 | An issue was discovered in certain Apple products. iOS before 11.2 is ... |
| CVE-2017-13803 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13802 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13798 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13796 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13795 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13794 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13793 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13792 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13791 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13788 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13785 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13784 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-13783 | An issue was discovered in certain Apple products. iOS before 11.1 is ... |
| CVE-2017-7165 | An issue was discovered in certain Apple products. iOS before 11.2 is ... |
| CVE-2017-7161 | An issue was discovered in certain Apple products. Safari before 11.0. ... |
| CVE-2017-7160 | An issue was discovered in certain Apple products. iOS before 11.2 is ... |
| CVE-2017-7157 | An issue was discovered in certain Apple products. iOS before 11.2 is ... |
| CVE-2017-7156 | An issue was discovered in certain Apple products. iOS before 11.2 is ... |
| CVE-2017-7153 | An issue was discovered in certain Apple products. iOS before 11.2 is ... |
| CVE-2017-7142 | An issue was discovered in certain Apple products. Safari before 11 is ... |
| CVE-2017-7120 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7117 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7111 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7109 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7107 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7104 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7102 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7100 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7099 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7098 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7096 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7095 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7094 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7093 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7092 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7091 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7090 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7089 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7087 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7081 | An issue was discovered in certain Apple products. iOS before 11 is af ... |
| CVE-2017-7064 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7061 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7059 | A DOMParser XSS issue was discovered in certain Apple products. iOS be ... |
| CVE-2017-7056 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7055 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7052 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7049 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7048 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7046 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7043 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7042 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7041 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7040 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7039 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7038 | A DOMParser XSS issue was discovered in certain Apple products. iOS be ... |
| CVE-2017-7037 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7034 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7030 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7020 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7019 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7018 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7012 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7011 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-7006 | An issue was discovered in certain Apple products. iOS before 10.3.3 i ... |
| CVE-2017-6984 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-6980 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2549 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2547 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2544 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2539 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2538 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2536 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2531 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2530 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2528 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2526 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2525 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2521 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2515 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2514 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2510 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2508 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2506 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2505 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2504 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2496 | An issue was discovered in certain Apple products. iOS before 10.3.2 i ... |
| CVE-2017-2481 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2476 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2475 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2471 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2470 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2469 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2468 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2466 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2465 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2464 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2460 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2459 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2457 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2455 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2454 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2447 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2446 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2445 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2442 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2433 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2424 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2419 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2415 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2405 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2396 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2395 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2394 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2392 | An issue was discovered in certain Apple products. Safari before 10.1 ... |
| CVE-2017-2386 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2377 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2376 | An issue was discovered in certain Apple products. iOS before 10.3 is ... |
| CVE-2017-2373 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2371 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2369 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2366 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2365 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2364 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2363 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2362 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2356 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2355 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2354 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2017-2350 | An issue was discovered in certain Apple products. iOS before 10.2.1 i ... |
| CVE-2016-7656 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7654 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7652 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7649 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7648 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7646 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7645 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7642 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7641 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7640 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7639 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7635 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7632 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7623 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7611 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7610 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7599 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7598 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7592 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7589 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7587 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-7586 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-4743 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-4692 | An issue was discovered in certain Apple products. iOS before 10.2 is ... |
| CVE-2016-4624 | WebKit in Apple iOS before 9.3.3, Safari before 9.1.2, and tvOS before ... |
| CVE-2016-4622 | WebKit in Apple iOS before 9.3.3, Safari before 9.1.2, and tvOS before ... |
| CVE-2016-4591 | WebKit in Apple iOS before 9.3.3, Safari before 9.1.2, and tvOS before ... |
| CVE-2016-4590 | WebKit in Apple iOS before 9.3.3 and Safari before 9.1.2 mishandles ab ... |
| CVE-2015-7098 | WebKit in Apple iOS before 9.2, Safari before 9.0.2, and tvOS before 9 ... |
| CVE-2015-7096 | WebKit in Apple iOS before 9.2, Safari before 9.0.2, and tvOS before 9 ... |
| CVE-2014-1745 | Use-after-free vulnerability in the SVG implementation in Blink, as us ... |