This page was not yet optimized for use on mobile devices.
CVE-2018-0032
Data ?
Vulnerability ID | CVE-2018-0032 |
---|---|
Published on | 11.07.2018 18:29 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:o:juniper:junos:16.1x65:*:*:*:*:*:*:*, cpe:2.3:o:juniper:junos:16.1x65:-:*:*:*:*:*:*, cpe:2.3:o:juniper:junos:16.1x65:d20:*:*:*:*:*:*, cpe:2.3:o:juniper:junos:16.1x65:d30:*:*:*:*:*:*, cpe:2.3:o:juniper:junos:16.1x65:d35:*:*:*:*:*:*, cpe:2.3:o:juniper:junos:16.1x65:d40:*:*:*:*:*:*, cpe:2.3:o:juniper:junos:16.1x65:d48:*:*:*:*:*:*
- cpe:2.3:o:juniper:junos:16.1x65:d30:*:*:*:*:*:*
- cpe:2.3:o:juniper:junos:16.1x65:d35:*:*:*:*:*:*
- cpe:2.3:o:juniper:junos:16.1x65:d40:*:*:*:*:*:*
-
…
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.