This page was not yet optimized for use on mobile devices.
CVE-2018-10811
Vulnerability details
| Vulnerability ID | CVE-2018-10811 |
|---|---|
| Published on | 19.06.2018 21:29 |
| Severity | HIGH |
Vulnerable configurations
32 CPEs-
- cpe:2.3:a:strongswan:strongswan:5.0.1:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.0.2:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.0.3:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.0.4:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.1.0:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.1.1:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.1.2:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.1.3:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.2.0:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.2.1:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.2.2:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.2.3:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.3.0:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.3.1:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.3.2:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.3.3:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.3.4:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.3.5:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.4.0:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.5.0:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.5.1:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.5.2:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.5.3:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.6.0:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.6.1:*:*:*:*:*:*:*
- cpe:2.3:a:strongswan:strongswan:5.6.2:*:*:*:*:*:*:*
Vulnerable certificates
This CVE has no assigned vulnerable Common Criteria or FIPS 140 certificates.