This page was not yet optimized for use on mobile devices.
CVE-2022-1941
Data ?
Vulnerability ID | CVE-2022-1941 |
---|---|
Published on | 22.09.2022 15:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:google:protobuf-cpp:-:*:*:*:*:*:*:*,
cpe:2.3:a:google:protobuf-cpp:2.4.1:*:*:*:*:*:*:*,
cpe:2.3:a:google:protobuf-cpp:2.5.0:*:*:*:*:*:*:*,
cpe:2.3:a:google:protobuf-cpp:2.6.0:*:*:*:*:*:*:*,
cpe:2.3:a:google:protobuf-cpp:2.6.1:-:*:*:*:*:*:*,
cpe:2.3:a:google:protobuf-cpp:2.6.1:rc1:*:*:*:*:*:*,
cpe:2.3:a:google:protobuf-cpp:3.0.0:-:*:*:*:*:*:*,
cpe:2.3:a:google:protobuf-cpp:3.0.0:alpha1:*:*:*:*:*:*,
cpe:2.3:a:google:protobuf-cpp:3.0.0:alpha2:*:*:*:*:*:*,
cpe:2.3:a:google:protobuf-cpp:3.0.0:alpha3:*:*:*:*:*:*,
…
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.