This page was not yet optimized for use on mobile devices.
CVE-2016-1232
Data ?
Vulnerability ID | CVE-2016-1232 |
---|---|
Published on | 12.01.2016 20:59 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:prosody:prosody:-:*:*:*:*:*:*:*,
cpe:2.3:a:prosody:prosody:0.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:prosody:prosody:0.2.0:*:*:*:*:*:*:*,
cpe:2.3:a:prosody:prosody:0.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:prosody:prosody:0.4.0:*:*:*:*:*:*:*,
cpe:2.3:a:prosody:prosody:0.4.1:*:*:*:*:*:*:*,
cpe:2.3:a:prosody:prosody:0.4.2:*:*:*:*:*:*:*,
cpe:2.3:a:prosody:prosody:0.5.0:*:*:*:*:*:*:*,
cpe:2.3:a:prosody:prosody:0.5.1:*:*:*:*:*:*:*,
cpe:2.3:a:prosody:prosody:0.5.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.