This page was not yet optimized for use on mobile devices.
CVE-2017-18226
Data ?
Vulnerability ID | CVE-2017-18226 |
---|---|
Published on | 12.03.2018 04:29 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:jabberd2:jabberd2:2.1:*:*:*:*:*:*:*,
cpe:2.3:a:jabberd2:jabberd2:2.1.1:*:*:*:*:*:*:*,
cpe:2.3:a:jabberd2:jabberd2:2.1.2:*:*:*:*:*:*:*,
cpe:2.3:a:jabberd2:jabberd2:2.1.3:*:*:*:*:*:*:*,
cpe:2.3:a:jabberd2:jabberd2:2.1.4:*:*:*:*:*:*:*,
cpe:2.3:a:jabberd2:jabberd2:2.1.5:*:*:*:*:*:*:*,
cpe:2.3:a:jabberd2:jabberd2:2.1.6:*:*:*:*:*:*:*,
cpe:2.3:a:jabberd2:jabberd2:2.1.7:*:*:*:*:*:*:*,
cpe:2.3:a:jabberd2:jabberd2:2.1.8:*:*:*:*:*:*:*,
cpe:2.3:a:jabberd2:jabberd2:2.1.9:*:*:*:*:*:*:*,
…
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.