Vulnerabilities
Aggregated CVE / GHSA / KEV / OSV — filter by tag and category.
| ID | Title | |
|---|---|---|
| CVE-2014-3600 |
|
XXE (XML External Entity) in apache (CVE-2014-3600)
vulnerability in apache (CVE-2014-3600). Successful exploitation can lead to full system takeover.
|
| CVE-2015-1835 |
|
Vulnerability in apache (CVE-2015-1835)
vulnerability in apache (CVE-2015-1835). Data can be tampered with by attackers.
|
| CVE-2016-5002 |
|
XXE (XML External Entity) in apache (CVE-2016-5002)
vulnerability in apache (CVE-2016-5002). Successful exploitation can lead to full system takeover.
|
| CVE-2016-5003 |
|
Unsafe Deserialization in apache (CVE-2016-5003)
vulnerability in apache (CVE-2016-5003). Successful exploitation can lead to full system takeover.
|
| CVE-2017-14182 |
|
Vulnerability in dos (CVE-2017-14182)
vulnerability in dos (CVE-2017-14182). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-7733 |
|
Cross-Site Scripting (XSS) in fortinet (CVE-2017-7733)
cross-site scripting in fortinet (CVE-2017-7733). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5103 |
|
Vulnerability in google (CVE-2017-5103)
vulnerability in google (CVE-2017-5103). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5105 |
|
Vulnerability in google (CVE-2017-5105)
vulnerability in google (CVE-2017-5105). Data can be tampered with by attackers.
|
| CVE-2017-5106 |
|
Vulnerability in google (CVE-2017-5106)
vulnerability in google (CVE-2017-5106). Data can be tampered with by attackers.
|
| CVE-2017-5107 |
|
Vulnerability in google (CVE-2017-5107)
vulnerability in google (CVE-2017-5107). Confidential information can be exposed externally.
|
| CVE-2017-5108 |
|
Vulnerability in google (CVE-2017-5108)
vulnerability in google (CVE-2017-5108). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5109 |
|
Vulnerability in google (CVE-2017-5109)
vulnerability in google (CVE-2017-5109). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5110 |
|
Vulnerability in google (CVE-2017-5110)
vulnerability in google (CVE-2017-5110). Data can be tampered with by attackers.
|
| 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-5112 |
|
Buffer Overflow in google (CVE-2017-5112)
vulnerability in google (CVE-2017-5112). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5113 |
|
Out-of-Bounds Write in google (CVE-2017-5113)
out-of-bounds write in google (CVE-2017-5113). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5114 |
|
Buffer Overflow in google (CVE-2017-5114)
vulnerability in google (CVE-2017-5114). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5115 |
|
Vulnerability in google (CVE-2017-5115)
vulnerability in google (CVE-2017-5115). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5116 |
|
Vulnerability in google (CVE-2017-5116)
vulnerability in google (CVE-2017-5116). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5117 |
|
Information Disclosure in google (CVE-2017-5117)
vulnerability in google (CVE-2017-5117). Confidential information can be exposed externally.
|
| CVE-2017-5118 |
|
Vulnerability in google (CVE-2017-5118)
vulnerability in google (CVE-2017-5118). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5120 |
|
Vulnerability in google (CVE-2017-5120)
vulnerability in google (CVE-2017-5120). Data can be tampered with by attackers.
|
| CVE-2017-5121 |
|
Vulnerability in google (CVE-2017-5121)
vulnerability in google (CVE-2017-5121). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5104 |
|
Vulnerability in google (CVE-2017-5104)
vulnerability in google (CVE-2017-5104). Data can be tampered with by attackers.
|
| CVE-2017-5119 |
|
Buffer Overflow in google (CVE-2017-5119)
vulnerability in google (CVE-2017-5119). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5122 |
|
Buffer Overflow in google (CVE-2017-5122)
vulnerability in google (CVE-2017-5122). 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-5075 |
|
Information Disclosure in google (CVE-2017-5075)
vulnerability in google (CVE-2017-5075). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5076 |
|
Vulnerability in google (CVE-2017-5076)
vulnerability in google (CVE-2017-5076). Data can be tampered with by attackers.
|
| CVE-2017-5077 |
|
Out-of-Bounds Read in google (CVE-2017-5077)
vulnerability in google (CVE-2017-5077). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5078 |
|
Vulnerability in c (CVE-2017-5078)
vulnerability in c (CVE-2017-5078). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5079 |
|
Vulnerability in google (CVE-2017-5079)
vulnerability in google (CVE-2017-5079). Risk of unauthorized operations or information disclosure.
|
| 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-5081 |
|
Vulnerability in google (CVE-2017-5081)
vulnerability in google (CVE-2017-5081). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5083 |
|
Vulnerability in google (CVE-2017-5083)
vulnerability in google (CVE-2017-5083). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5086 |
|
Vulnerability in google (CVE-2017-5086)
vulnerability in google (CVE-2017-5086). Data can be tampered with by attackers.
|
| 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-5088 |
|
Out-of-Bounds Read in google (CVE-2017-5088)
vulnerability in google (CVE-2017-5088). 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-5092 |
|
Vulnerability in google (CVE-2017-5092)
vulnerability in google (CVE-2017-5092). Successful exploitation can lead to full system takeover.
|
| CVE-2017-5093 |
|
Vulnerability in google (CVE-2017-5093)
vulnerability in google (CVE-2017-5093). Data can be tampered with by attackers.
|
| CVE-2017-5094 |
|
Vulnerability in c (CVE-2017-5094)
vulnerability in c (CVE-2017-5094). Data can be tampered with by attackers.
|
| CVE-2017-5095 |
|
Out-of-Bounds Write in google (CVE-2017-5095)
out-of-bounds write in google (CVE-2017-5095). 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-5101 |
|
Vulnerability in google (CVE-2017-5101)
vulnerability in google (CVE-2017-5101). Data can be tampered with by attackers.
|
| CVE-2017-5102 |
|
Vulnerability in google (CVE-2017-5102)
vulnerability in google (CVE-2017-5102). Risk of unauthorized operations or information disclosure.
|
| CVE-2017-5089 |
|
Vulnerability in google (CVE-2017-5089)
vulnerability in google (CVE-2017-5089). Data can be tampered with by attackers.
|
| CVE-2017-5090 |
|
Vulnerability in google (CVE-2017-5090)
vulnerability in google (CVE-2017-5090). Data can be tampered with by attackers.
|
| CVE-2017-5082 |
|
Information Disclosure in google (CVE-2017-5082)
vulnerability in google (CVE-2017-5082). Confidential information can be exposed externally.
|