This page was not yet optimized for use on mobile devices.
CVE-2016-0779
Data ?
Vulnerability ID | CVE-2016-0779 |
---|---|
Published on | 11.04.2017 16:59 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:apache:tomee:-:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomee:1.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomee:1.0.0:beta1:*:*:*:*:*:*,
cpe:2.3:a:apache:tomee:1.0.0:beta2:*:*:*:*:*:*,
cpe:2.3:a:apache:tomee:1.5.0:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomee:1.5.1:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomee:1.5.2:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomee:1.6.0:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomee:1.6.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:apache:tomee:1.6.0.2:*:*:*:*:*:*:*,
…
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.