This page was not yet optimized for use on mobile devices.
CVE-2016-9391
Data ?
Vulnerability ID | CVE-2016-9391 |
---|---|
Published on | 23.03.2017 18:59 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:jasper_project:jasper:-:*:*:*:*:*:*:*,
cpe:2.3:a:jasper_project:jasper:1.900.1:*:*:*:*:*:*:*,
cpe:2.3:a:jasper_project:jasper:1.900.2:*:*:*:*:*:*:*,
cpe:2.3:a:jasper_project:jasper:1.900.3:*:*:*:*:*:*:*,
cpe:2.3:a:jasper_project:jasper:1.900.4:*:*:*:*:*:*:*,
cpe:2.3:a:jasper_project:jasper:1.900.5:*:*:*:*:*:*:*,
cpe:2.3:a:jasper_project:jasper:1.900.6:*:*:*:*:*:*:*,
cpe:2.3:a:jasper_project:jasper:1.900.7:*:*:*:*:*:*:*,
cpe:2.3:a:jasper_project:jasper:1.900.8:*:*:*:*:*:*:*,
cpe:2.3:a:jasper_project:jasper:1.900.9:*:*:*:*:*:*:*,
…
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.