This page was not yet optimized for use on mobile devices.
CVE-2022-3515
Data ?
Vulnerability ID | CVE-2022-3515 |
---|---|
Published on | 12.01.2023 15:15 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:gpg4win:gpg4win:2.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:gpg4win:gpg4win:3.0.3:*:*:*:*:*:*:*,
cpe:2.3:a:gpg4win:gpg4win:3.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:gpg4win:gpg4win:3.1.1:*:*:*:*:*:*:*,
cpe:2.3:a:gpg4win:gpg4win:3.1.2:*:*:*:*:*:*:*,
cpe:2.3:a:gpg4win:gpg4win:3.1.3:*:*:*:*:*:*:*,
cpe:2.3:a:gpg4win:gpg4win:3.1.4:*:*:*:*:*:*:*,
cpe:2.3:a:gpg4win:gpg4win:3.1.5:*:*:*:*:*:*:*,
cpe:2.3:a:gpg4win:gpg4win:3.1.5-1:*:*:*:*:*:*:*,
cpe:2.3:a:gpg4win:gpg4win:3.1.6:*:*:*:*:*:*:*,
…
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.