This page was not yet optimized for use on mobile devices.
CVE-2012-5642
Data ?
Vulnerability ID | CVE-2012-5642 |
---|---|
Published on | 31.12.2012 11:50 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:fail2ban:fail2ban:-:*:*:*:*:*:*:*,
cpe:2.3:a:fail2ban:fail2ban:0.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:fail2ban:fail2ban:0.1.1:*:*:*:*:*:*:*,
cpe:2.3:a:fail2ban:fail2ban:0.1.2:*:*:*:*:*:*:*,
cpe:2.3:a:fail2ban:fail2ban:0.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:fail2ban:fail2ban:0.3.1:*:*:*:*:*:*:*,
cpe:2.3:a:fail2ban:fail2ban:0.4.0:*:*:*:*:*:*:*,
cpe:2.3:a:fail2ban:fail2ban:0.4.1:*:*:*:*:*:*:*,
cpe:2.3:a:fail2ban:fail2ban:0.5.0:*:*:*:*:*:*:*,
cpe:2.3:a:fail2ban:fail2ban:0.5.1:*:*:*:*:*:*:*,
…
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.