This page was not yet optimized for use on mobile devices.
CVE-2016-8735
Data ?
Vulnerability ID | CVE-2016-8735 |
---|---|
Published on | 06.04.2017 21:59 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:apache:tomcat:-:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomcat:1.1.3:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomcat:3.0:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomcat:3.1:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomcat:3.1.1:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomcat:3.2:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomcat:3.2.1:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomcat:3.2.2:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomcat:3.2.2:beta2:*:*:*:*:*:*,
cpe:2.3:a:apache:tomcat:3.2.3:*:*:*:*:*:*:*,
…
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.