This page was not yet optimized for use on mobile devices.
CVE-2016-4800
Data ?
Vulnerability ID | CVE-2016-4800 |
---|---|
Published on | 13.04.2017 14:59 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:eclipse:jetty:9.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:eclipse:jetty:9.3.0:20150601:*:*:*:*:*:*,
cpe:2.3:a:eclipse:jetty:9.3.0:20150608:*:*:*:*:*:*,
cpe:2.3:a:eclipse:jetty:9.3.0:20150612:*:*:*:*:*:*,
cpe:2.3:a:eclipse:jetty:9.3.0:m2:*:*:*:*:*:*,
cpe:2.3:a:eclipse:jetty:9.3.0:maintenance_0:*:*:*:*:*:*,
cpe:2.3:a:eclipse:jetty:9.3.0:maintenance_1:*:*:*:*:*:*,
cpe:2.3:a:eclipse:jetty:9.3.0:maintenance0:*:*:*:*:*:*,
cpe:2.3:a:eclipse:jetty:9.3.0:maintenance1:*:*:*:*:*:*,
cpe:2.3:a:eclipse:jetty:9.3.0:maintenance2:*:*:*:*:*:*,
…
running on/with
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.