Vulnerabilities
Aggregated CVE / GHSA / KEV / OSV — filter by tag and category.
| ID | Title | |
|---|---|---|
| CVE-2017-10946 |
|
Use-After-Free in foxitsoftware (CVE-2017-10946)
vulnerability in foxitsoftware (CVE-2017-10946). Successful exploitation can lead to full system takeover.
|
| CVE-2017-10947 |
|
Use-After-Free in foxitsoftware (CVE-2017-10947)
vulnerability in foxitsoftware (CVE-2017-10947). Successful exploitation can lead to full system takeover.
|
| CVE-2017-10948 |
|
Use-After-Free in foxitsoftware (CVE-2017-10948)
vulnerability in foxitsoftware (CVE-2017-10948). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5111 |
|
Use-After-Free in google (CVE-2017-5111)
vulnerability in google (CVE-2017-5111). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5074 |
|
Use-After-Free in google (CVE-2017-5074)
vulnerability in google (CVE-2017-5074). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5080 |
|
Use-After-Free in google (CVE-2017-5080)
vulnerability in google (CVE-2017-5080). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5087 |
|
Use-After-Free in google (CVE-2017-5087)
vulnerability in google (CVE-2017-5087). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5091 |
|
Use-After-Free in google (CVE-2017-5091)
vulnerability in google (CVE-2017-5091). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5098 |
|
Use-After-Free in google (CVE-2017-5098)
vulnerability in google (CVE-2017-5098). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5100 |
|
Use-After-Free in google (CVE-2017-5100)
vulnerability in google (CVE-2017-5100). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5055 |
|
Out-of-Bounds Read in google (CVE-2017-5055)
vulnerability in google (CVE-2017-5055). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5056 |
|
Use-After-Free in google (CVE-2017-5056)
vulnerability in google (CVE-2017-5056). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5058 |
|
Use-After-Free in google (CVE-2017-5058)
vulnerability in google (CVE-2017-5058). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5062 |
|
Use-After-Free in google (CVE-2017-5062)
vulnerability in google (CVE-2017-5062). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5073 |
|
Use-After-Free in google (CVE-2017-5073)
vulnerability in google (CVE-2017-5073). Successful exploitation can lead to full system takeover.
|
| CVE-2017-15227 |
|
Use-After-Free in irssi (CVE-2017-15227)
vulnerability in irssi (CVE-2017-15227). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-15642 |
|
Use-After-Free in c (CVE-2017-15642)
vulnerability in c (CVE-2017-15642). Risk of unauthorized operations or information disclosure.
|
| CVE-2015-7687 |
|
Use-After-Free in dos (CVE-2015-7687)
vulnerability in dos (CVE-2015-7687). Successful exploitation can lead to full system takeover.
|
| CVE-2017-15265 |
|
Vulnerability in c (CVE-2017-15265)
vulnerability in c (CVE-2017-15265). Successful exploitation can lead to full system takeover.
|
| CVE-2017-15369 |
|
Use-After-Free in c (CVE-2017-15369)
vulnerability in c (CVE-2017-15369). Successful exploitation can lead to full system takeover.
|
| CVE-2017-15238 |
|
Use-After-Free in c (CVE-2017-15238)
vulnerability in c (CVE-2017-15238). Successful exploitation can lead to full system takeover.
|
| CVE-2017-11048 |
|
Use-After-Free in google (CVE-2017-11048)
vulnerability in google (CVE-2017-11048). Successful exploitation can lead to full system takeover.
|
| CVE-2017-14989 |
|
Use-After-Free in c (CVE-2017-14989)
vulnerability in c (CVE-2017-14989). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-9790 |
|
Use-After-Free in apache (CVE-2017-9790)
vulnerability in apache (CVE-2017-9790). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-14857 |
|
Use-After-Free in cpp (CVE-2017-14857)
vulnerability in cpp (CVE-2017-14857). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-8277 |
|
Use-After-Free in google (CVE-2017-8277)
vulnerability in google (CVE-2017-8277). Successful exploitation can lead to full system takeover.
|
| CVE-2017-9676 |
|
Information Disclosure in google (CVE-2017-9676)
vulnerability in google (CVE-2017-9676). Confidential information can be exposed externally.
|
| CVE-2015-6673 |
|
Use-after-free vulnerability in Decoder.cpp in libpgf before 6.15.32.
Use-after-free vulnerability in Decoder.cpp in libpgf before 6.15.32.
|
| CVE-2015-3890 |
|
Use-after-free vulnerability in Open Litespeed before 1.3.10.
Use-after-free vulnerability in Open Litespeed before 1.3.10.
|
| CVE-2015-1329 |
|
Use-After-Free in canonical (CVE-2015-1329)
vulnerability in canonical (CVE-2015-1329). Successful exploitation can lead to full system takeover.
|
| CVE-2017-9798 |
|
Use-After-Free in c (CVE-2017-9798)
vulnerability in c (CVE-2017-9798). Confidential information can be exposed externally.
|
| CVE-2017-14528 |
|
Use-After-Free in c (CVE-2017-14528)
vulnerability in c (CVE-2017-14528). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-12133 |
|
Use-After-Free in c (CVE-2017-12133)
vulnerability in c (CVE-2017-12133). Data can be tampered with by attackers.
|
| CVE-2017-2808 |
|
Use-After-Free in ledger-cli (CVE-2017-2808)
vulnerability in ledger-cli (CVE-2017-2808). Successful exploitation can lead to full system takeover.
|
| CVE-2017-2821 |
|
Use-After-Free in lexmark (CVE-2017-2821)
vulnerability in lexmark (CVE-2017-2821). Successful exploitation can lead to full system takeover.
|
| CVE-2017-13711 |
|
Use-After-Free in c (CVE-2017-13711)
vulnerability in c (CVE-2017-13711). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-14103 |
|
Use-After-Free in c (CVE-2017-14103)
vulnerability in c (CVE-2017-14103). Successful exploitation can lead to full system takeover.
|
| CVE-2017-13737 |
|
Use-After-Free in c (CVE-2017-13737)
vulnerability in c (CVE-2017-13737). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-13741 |
|
Use-After-Free in c (CVE-2017-13741)
vulnerability in c (CVE-2017-13741). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-12877 |
|
Use-After-Free in c (CVE-2017-12877)
vulnerability in c (CVE-2017-12877). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-10661 |
|
Use-After-Free in c (CVE-2017-10661)
vulnerability in c (CVE-2017-10661). Successful exploitation can lead to full system takeover.
|
| CVE-2017-7364 |
|
Use-After-Free in google (CVE-2017-7364)
vulnerability in google (CVE-2017-7364). Successful exploitation can lead to full system takeover.
|
| CVE-2017-9684 |
|
Vulnerability in google (CVE-2017-9684)
vulnerability in google (CVE-2017-9684). Successful exploitation can lead to full system takeover.
|
| CVE-2017-9685 |
|
Vulnerability in google (CVE-2017-9685)
vulnerability in google (CVE-2017-9685). Successful exploitation can lead to full system takeover.
|
| CVE-2017-8262 |
|
Vulnerability in google (CVE-2017-8262)
vulnerability in google (CVE-2017-8262). Successful exploitation can lead to full system takeover.
|
| CVE-2017-8266 |
|
Vulnerability in google (CVE-2017-8266)
vulnerability in google (CVE-2017-8266). Successful exploitation can lead to full system takeover.
|
| CVE-2017-8270 |
|
Vulnerability in google (CVE-2017-8270)
vulnerability in google (CVE-2017-8270). Successful exploitation can lead to full system takeover.
|
| CVE-2016-10385 |
|
Use-After-Free in google (CVE-2016-10385)
vulnerability in google (CVE-2016-10385). Successful exploitation can lead to full system takeover.
|
| CVE-2017-12936 |
|
Use-After-Free in c (CVE-2017-12936)
vulnerability in c (CVE-2017-12936). Successful exploitation can lead to full system takeover.
|
| CVE-2017-12932 |
|
Use-After-Free in CVE-2017-12932 (CVE-2017-12932)
vulnerability in CVE-2017-12932 (CVE-2017-12932). Successful exploitation can lead to full system takeover.
|