CVE-2014-5075
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| redhat | jboss_fuse | {"endIncluding":"6.1.0"} | |
| igniterealtime | smack_api | {"endIncluding":"4.0.1"} | |
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
CWEs
CWE-310
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.