This page was not yet optimized for use on mobile devices.
CVE-2021-32642
Data ?
Vulnerability ID | CVE-2021-32642 |
---|---|
Published on | 28.05.2021 17:15 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:uninett:radsecproxy:1.0:*:*:*:*:*:*:*,
cpe:2.3:a:uninett:radsecproxy:1.0:alpha:*:*:*:*:*:*,
cpe:2.3:a:uninett:radsecproxy:1.0:alpha-p1:*:*:*:*:*:*,
cpe:2.3:a:uninett:radsecproxy:1.0:p1:*:*:*:*:*:*,
cpe:2.3:a:uninett:radsecproxy:1.1:*:*:*:*:*:*:*,
cpe:2.3:a:uninett:radsecproxy:1.1:alpha:*:*:*:*:*:*,
cpe:2.3:a:uninett:radsecproxy:1.1:beta:*:*:*:*:*:*,
cpe:2.3:a:uninett:radsecproxy:1.2:*:*:*:*:*:*:*,
cpe:2.3:a:uninett:radsecproxy:1.3:alpha:*:*:*:*:*:*,
cpe:2.3:a:uninett:radsecproxy:1.3:beta:*:*:*:*:*:*,
…
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.