This page was not yet optimized for use on mobile devices.
CVE-2020-1942
Data ?
Vulnerability ID | CVE-2020-1942 |
---|---|
Published on | 11.02.2020 21:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:apache:nifi:0.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:0.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:0.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:0.2.0:*:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:0.2.1:*:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:0.2.1:-:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:0.2.1:rc1:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:0.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:0.3.0:-:*:*:*:*:*:*,
cpe:2.3:a:apache:nifi:0.3.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.