This page was not yet optimized for use on mobile devices.
CVE-2016-6313
Data ?
Vulnerability ID | CVE-2016-6313 |
---|---|
Published on | 13.12.2016 20:59 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:gnupg:libgcrypt:-:*:*:*:*:*:*:*,
cpe:2.3:a:gnupg:libgcrypt:0.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:gnupg:libgcrypt:0.2.0:*:*:*:*:*:*:*,
cpe:2.3:a:gnupg:libgcrypt:0.2.6:*:*:*:*:*:*:*,
cpe:2.3:a:gnupg:libgcrypt:0.2.8:*:*:*:*:*:*:*,
cpe:2.3:a:gnupg:libgcrypt:0.2.10:*:*:*:*:*:*:*,
cpe:2.3:a:gnupg:libgcrypt:0.2.15:*:*:*:*:*:*:*,
cpe:2.3:a:gnupg:libgcrypt:0.2.17:*:*:*:*:*:*:*,
cpe:2.3:a:gnupg:libgcrypt:0.2.18:*:*:*:*:*:*:*,
cpe:2.3:a:gnupg:libgcrypt:0.2.19:*:*:*:*:*:*:*,
…
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.