This page was not yet optimized for use on mobile devices.
CVE-2013-6411
Data ?
Vulnerability ID | CVE-2013-6411 |
---|---|
Published on | 14.12.2013 17:21 |
Severity | MEDIUM |
Vulnerable configurations ?
- cpe:2.3:a:openttd:openttd:0.3.6:*:*:*:*:*:*:*
- cpe:2.3:a:openttd:openttd:0.4.0:*:*:*:*:*:*:*
- cpe:2.3:a:openttd:openttd:0.4.0.1:*:*:*:*:*:*:*
- cpe:2.3:a:openttd:openttd:0.4.5:*:*:*:*:*:*:*
- cpe:2.3:a:openttd:openttd:0.4.6:*:*:*:*:*:*:*
- cpe:2.3:a:openttd:openttd:0.4.7:*:*:*:*:*:*:*
- cpe:2.3:a:openttd:openttd:0.4.8:*:*:*:*:*:*:*
- cpe:2.3:a:openttd:openttd:0.5.0:*:*:*:*:*:*:*
- cpe:2.3:a:openttd:openttd:0.5.1:*:*:*:*:*:*:*
- cpe:2.3:a:openttd:openttd:0.5.2:*:*:*:*:*:*:*
-
…
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.