This page was not yet optimized for use on mobile devices.
CVE-2016-20021
Data ?
Vulnerability ID | CVE-2016-20021 |
---|---|
Published on | 12.01.2024 03:15 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:gentoo:portage:-:*:*:*:*:*:*:*,
cpe:2.3:a:gentoo:portage:2.0.50:-:*:*:*:*:*:*,
cpe:2.3:a:gentoo:portage:2.0.51.22:r3:*:*:*:*:*:*,
cpe:2.3:a:gentoo:portage:2.1.1:r2:*:*:*:*:*:*,
cpe:2.3:a:gentoo:portage:2.1.3.10:*:*:*:*:*:*:*,
cpe:2.3:a:gentoo:portage:2.1.4.4:*:*:*:*:*:*:*,
cpe:2.3:a:gentoo:portage:2.3.79:*:*:*:*:*:*:*,
cpe:2.3:a:gentoo:portage:2.3.80:*:*:*:*:*:*:*,
cpe:2.3:a:gentoo:portage:2.3.81:*:*:*:*:*:*:*,
cpe:2.3:a:gentoo:portage:2.3.82:*:*:*:*:*:*:*,
…
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.