This page was not yet optimized for use on mobile devices.
CVE-2022-25761
Data ?
Vulnerability ID | CVE-2022-25761 |
---|---|
Published on | 23.08.2022 05:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:open62541:open62541:0.1:-:*:*:*:*:*:*,
cpe:2.3:a:open62541:open62541:0.1.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:open62541:open62541:0.1.0:rc2:*:*:*:*:*:*,
cpe:2.3:a:open62541:open62541:0.1.0:rc3.3:*:*:*:*:*:*,
cpe:2.3:a:open62541:open62541:0.1.0:rc4:*:*:*:*:*:*,
cpe:2.3:a:open62541:open62541:0.1.1:*:*:*:*:*:*:*,
cpe:2.3:a:open62541:open62541:0.2:-:*:*:*:*:*:*,
cpe:2.3:a:open62541:open62541:0.2:rc2:*:*:*:*:*:*,
cpe:2.3:a:open62541:open62541:0.2.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:open62541:open62541:0.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.