How severe is CVE-2012-5811?

CVE-2012-5811 has a CVSS 2.0 base score of 5.8, rated medium severity.

Is CVE-2012-5811 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (43rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2012-5811?

CVE-2012-5811 affects Breezy. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2012-5811?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2012-5811 published?

CVE-2012-5811 was published on 2012-11-04 and last updated on 2026-06-16.

CVE-2012-5811

CVE-2012-5811 is a medium-severity vulnerability in Breezy with a CVSS 2.0 base score of 5.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-310.

Key facts

Severity: Medium (CVSS 2.0 base score 5.8)
EPSS exploit prediction: 1% (43rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-310
Affected product: Breezy
Published: 2012-11-04
Last modified: 2026-06-16

Description

The Breezy application for Android does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

Frequently asked questions

What is CVE-2012-5811?: The Breezy application for Android does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
How severe is CVE-2012-5811?: CVE-2012-5811 has a CVSS 2.0 base score of 5.8, rated medium severity.
Is CVE-2012-5811 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (43rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-5811?: CVE-2012-5811 affects Breezy. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2012-5811?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2012-5811 published?: CVE-2012-5811 was published on 2012-11-04 and last updated on 2026-06-16.

References

http://www.cs.utexas.edu/~shmat/shmat_ccs12.pdf

Affected products (1)

cpe:2.3:a:breezy:breezy:-:-:*:*:*:android:*:*

Other CWE-310 (Cryptographic Issues) vulnerabilities

CVE-2014-7878 — Critical (CVSS 10.0): The Application Lifecycle Service (ALS) in HP Helion Cloud Development Platform 1.0, when a virtual machine is derived…
CVE-2013-3712 — Critical (CVSS 10.0): SUSE Studio Onsite 1.3.x before 1.3.6 and SUSE Studio Extension for System z 1.3 uses "static" secret tokens, which has…
CVE-2013-6952 — Critical (CVSS 10.0): The Belkin WeMo Home Automation firmware before 3949 has a hardcoded GPG key, which makes it easier for remote…
CVE-2013-6838 — Critical (CVSS 10.0): An unspecified Enghouse Interactive Professional Services "addon product" in Enghouse Interactive IVR Pro (VIP2000)…
CVE-2013-0137 — Critical (CVSS 10.0): The default configuration of the Digital Alert Systems DASDEC EAS device before 2.0-2 and the Monroe Electronics R189…
CVE-2011-5123 — Critical (CVSS 10.0): The Antivirus component in Comodo Internet Security before 5.3.175888.1227 does not check whether X.509 certificates in…

Browse all CWE-310 (Cryptographic Issues) vulnerabilities →