This page was not yet optimized for use on mobile devices.
CVE-2016-1572
Data ?
Vulnerability ID | CVE-2016-1572 |
---|---|
Published on | 22.01.2016 15:59 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:ecryptfs:ecryptfs-utils:-:*:*:*:*:*:*:*,
cpe:2.3:a:ecryptfs:ecryptfs-utils:58:*:*:*:*:*:*:*,
cpe:2.3:a:ecryptfs:ecryptfs-utils:60:*:*:*:*:*:*:*,
cpe:2.3:a:ecryptfs:ecryptfs-utils:61:*:*:*:*:*:*:*,
cpe:2.3:a:ecryptfs:ecryptfs-utils:62:*:*:*:*:*:*:*,
cpe:2.3:a:ecryptfs:ecryptfs-utils:63:*:*:*:*:*:*:*,
cpe:2.3:a:ecryptfs:ecryptfs-utils:64:*:*:*:*:*:*:*,
cpe:2.3:a:ecryptfs:ecryptfs-utils:65:*:*:*:*:*:*:*,
cpe:2.3:a:ecryptfs:ecryptfs-utils:66:*:*:*:*:*:*:*,
cpe:2.3:a:ecryptfs:ecryptfs-utils:67:*:*:*:*:*:*:*,
…
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.