This page was not yet optimized for use on mobile devices.
CVE-2016-10327
Data ?
| Vulnerability ID | CVE-2016-10327 |
|---|---|
| Published on | 14.04.2017 04:59 |
| Severity | CRITICAL |
Vulnerable configurations ?
- cpe:2.3:a:libreoffice:libreoffice:3.6.0.0:beta2:*:*:*:*:*:*, cpe:2.3:a:libreoffice:libreoffice:4.0.0.0:beta2:*:*:*:*:*:*, cpe:2.3:a:libreoffice:libreoffice:4.1.0.0:beta2:*:*:*:*:*:*, cpe:2.3:a:libreoffice:libreoffice:4.2.0.0:beta2:*:*:*:*:*:*, cpe:2.3:a:libreoffice:libreoffice:4.3.0.0:beta2:*:*:*:*:*:*, cpe:2.3:a:libreoffice:libreoffice:4.4.0.0:beta2:*:*:*:*:*:*, cpe:2.3:a:libreoffice:libreoffice:5.0.0.0:beta2:*:*:*:*:*:*, cpe:2.3:a:libreoffice:libreoffice:5.1.0.0:beta2:*:*:*:*:*:*, cpe:2.3:a:libreoffice:libreoffice:5.2.0.0:beta2:*:*:*:*:*:*, cpe:2.3:a:libreoffice:libreoffice:5.3.0.0:beta2:*:*:*:*:*:*
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.