ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
---|---|---|---|---|---|
CVE-2016-0640 | 2016-04-21 | 2025-04-12 | 6.1 | 4.9 | Unknown |
CVE-2016-0641 | 2016-04-21 | 2025-04-12 | 5.1 | 4.9 | Unknown |
CVE-2016-0643 | 2016-04-21 | 2025-04-12 | 3.3 | 4.0 | Likely |
CVE-2016-0644 | 2016-04-21 | 2025-04-12 | 5.5 | 4.0 | Likely |
CVE-2016-0646 | 2016-04-21 | 2025-04-12 | 5.5 | 4.0 | Likely |
CVE-2016-0647 | 2016-04-21 | 2025-04-12 | 5.5 | 4.0 | Likely |
CVE-2016-0648 | 2016-04-21 | 2025-04-12 | 5.5 | 4.0 | Likely |
CVE-2016-0649 | 2016-04-21 | 2025-04-12 | 5.5 | 4.0 | Likely |
CVE-2016-0650 | 2016-04-21 | 2025-04-12 | 5.5 | 4.0 | Likely |
CVE-2016-0666 | 2016-04-21 | 2025-04-12 | 5.5 | 3.5 | Unknown |
CVE-2016-3452 | 2016-07-21 | 2025-04-12 | 3.7 | 4.3 | Likely |
CVE-2016-3477 | 2016-07-21 | 2025-04-12 | 8.1 | 4.1 | Unknown |
CVE-2016-3521 | 2016-07-21 | 2025-04-12 | 6.5 | 6.8 | Likely |
CVE-2016-3615 | 2016-07-21 | 2025-04-12 | 5.3 | 4.3 | Likely |
CVE-2016-5440 | 2016-07-21 | 2025-04-12 | 4.9 | 4.0 | Likely |
CVE-2016-5444 | 2016-07-21 | 2025-04-12 | 3.7 | 4.3 | Likely |
CVE-2016-3044 | 2016-12-01 | 2025-04-12 | 6.5 | 4.9 | Unknown |
CVE-2015-3217 | 2016-12-13 | 2025-04-12 | 7.5 | 5.0 | Likely |
CVE-2015-5073 | 2016-12-13 | 2025-04-12 | 9.1 | 6.4 | Likely |
CVE-2016-5011 | 2017-04-11 | 2025-04-20 | 4.6 | 4.9 | Unknown |