CVE-2014-5075
The Ignite Realtime Smack XMPP API 4.x before 4.0.2, and 3.x and 2.x when a custom SSLContext is used, 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,…
Does this matter?
Lower severity and a low EPSS score (0.92%). Track it; it rarely justifies an emergency change on its own.
Description
The Ignite Realtime Smack XMPP API 4.x before 4.0.2, and 3.x and 2.x when a custom SSLContext is used, 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.
- CVSS 2.0
- 6.8 MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
- EPSS
- 0.92% probability · 58th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-310
- Affected
- redhat/jboss fuse · igniterealtime/smack api
- Source
- cve@mitre.org
References
- http://op-co.de/CVE-2014-5075.html
- http://rhn.redhat.com/errata/RHSA-2015-1176.html
- http://secunia.com/advisories/59915
- http://www.securityfocus.com/bid/69064
- http://op-co.de/CVE-2014-5075.html
- http://rhn.redhat.com/errata/RHSA-2015-1176.html
- http://secunia.com/advisories/59915
- http://www.securityfocus.com/bid/69064
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.