This page was not yet optimized for use on mobile devices.
CVE-2017-5529
Data ?
| Vulnerability ID | CVE-2017-5529 |
|---|---|
| Published on | 29.06.2017 14:29 |
| Severity | MEDIUM |
Vulnerable configurations ?
- cpe:2.3:a:tibco:jasperreports_professional:6.2.1:*:*:*:*:*:*:*
- cpe:2.3:a:tibco:jasperreports_professional:6.3.0:*:*:*:*:*:*:*
- cpe:2.3:a:tibco:jasperreports_server:-:*:*:*:-:-:*:*, cpe:2.3:a:tibco:jasperreports_server:6.1.1:*:*:*:*:activematrix_bpm:*:*, cpe:2.3:a:tibco:jasperreports_server:6.1.1:*:*:*:-:-:*:*
- cpe:2.3:a:tibco:jasperreports_server:6.2.0:*:*:*:*:activematrix_bpm:*:*, cpe:2.3:a:tibco:jasperreports_server:6.2.0:*:*:*:-:-:*:*, cpe:2.3:a:tibco:jasperreports_server:6.2.0:*:*:*:community:*:*:*
-
cpe:2.3:a:tibco:jasperreports_server:6.2.1:*:*:*:*:activematrix_bpm:*:*,
cpe:2.3:a:tibco:jasperreports_server:6.2.1:*:*:*:-:-:*:*,
…
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.