This page was not yet optimized for use on mobile devices.
CVE-2018-17540
Data
| Vulnerability ID | CVE-2018-17540 |
|---|---|
| Published on | 03.10.2018 20:29 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:strongswan:strongswan:2.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:strongswan:strongswan:2.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:strongswan:strongswan:2.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:strongswan:strongswan:2.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:strongswan:strongswan:2.1.1:*:*:*:*:*:*:*,
cpe:2.3:a:strongswan:strongswan:2.1.2:*:*:*:*:*:*:*,
cpe:2.3:a:strongswan:strongswan:2.1.3:*:*:*:*:*:*:*,
cpe:2.3:a:strongswan:strongswan:2.1.4:*:*:*:*:*:*:*,
cpe:2.3:a:strongswan:strongswan:2.1.5:*:*:*:*:*:*:*,
cpe:2.3:a:strongswan:strongswan:2.3.0:*:*:*:*:*:*:*,
…
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.