This page was not yet optimized for use on mobile devices.
CVE-2018-10612
Data ?
Vulnerability ID | CVE-2018-10612 |
---|---|
Published on | 29.01.2019 16:29 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:codesys:control_for_beaglebone_sl:3.0:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_for_beaglebone_sl:3.5.10.0:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_for_beaglebone_sl:3.5.10.20:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_for_beaglebone_sl:3.5.10.30:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_for_beaglebone_sl:3.5.11.0:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_for_beaglebone_sl:3.5.11.10:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_for_beaglebone_sl:3.5.11.20:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_for_beaglebone_sl:3.5.11.50:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_for_beaglebone_sl:3.5.11.60:*:*:*:*:*:*:*,
cpe:2.3:a:codesys:control_for_beaglebone_sl:3.5.12.0:*:*:*:*:*:*:*,
…
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.