This page was not yet optimized for use on mobile devices.
CVE-2017-5636
Data ?
Vulnerability ID | CVE-2017-5636 |
---|---|
Published on | 19.10.2017 20:29 |
Severity | CRITICAL |
Vulnerable configurations ?
- cpe:2.3:a:apache:nifi:0.7.0:*:*:*:*:*:*:*, cpe:2.3:a:apache:nifi:0.7.0:-:*:*:*:*:*:*, cpe:2.3:a:apache:nifi:0.7.0:rc1:*:*:*:*:*:*, cpe:2.3:a:apache:nifi:0.7.0:rc2:*:*:*:*:*:*
- cpe:2.3:a:apache:nifi:0.7.1:*:*:*:*:*:*:*, cpe:2.3:a:apache:nifi:0.7.1:-:*:*:*:*:*:*, cpe:2.3:a:apache:nifi:0.7.1:rc1:*:*:*:*:*:*
-
cpe:2.3:a:apache:nifi:1.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:1.1.0:-:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:1.1.0:rc1:*:*:*:*:*:*,
…
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.