CVE-2014-5075
First published: Wed Aug 06 2014(Updated: )
It was reported [1] that Smack (XMPP client library) is vulnerable to MitM attacks with a crafted SSL certificates. Quote from [1]: ... Details ------- Smack is using Java's `SSLSocket`, which checks the peer certificate using an `X509TrustManager`, but does not perform hostname verification. Therefore, it is possible to redirect the traffic between a Smack-using application and a legitimate XMPP server through the attacker's server, merely by providing a valid certificate for a domain under the attacker's control. In Smack versions 2.2.0 to 3.4.1, a custom `ServerTrustManager` implementation was used, which was supplied with the connection's server name, and performed hostname verification. However, it failed to verify the basicConstraints and nameConstraints of the certificate chain (<a href="https://access.redhat.com/security/cve/CVE-2014-0363">CVE-2014-0363</a>, <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0363">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0363</a>) and has been removed in Smack 4.0.0. Applications using Smack 2.2.0 to 3.4.1 with a custom `TrustManager` did not benefit from `ServerTrustManager` and are vulnerable as well, unless their own `TrustManager` implementation explicitly performs hostname verification. ... [1]: <a href="http://seclists.org/bugtraq/2014/Aug/29">http://seclists.org/bugtraq/2014/Aug/29</a>
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/smack-core | <4.0.2 | 4.0.2 |
| redhat/smack-tcp | <4.0.2 | 4.0.2 |
| redhat/smack | <4.0.2 | 4.0.2 |
| Red Hat JBoss Fuse | <=6.1.0 | |
| Ignite Realtime Smack API | <=4.0.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://access.redhat.com/security/cve/CVE-2014-0363
- http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0363
- http://seclists.org/bugtraq/2014/Aug/29
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1127277
- https://igniterealtime.org/issues/browse/SMACK-586
- http://fisheye.igniterealtime.org/changelog/smackgit?cs=057d00c9de04d576db40c4f2525a74dace9580b4
- https://rhn.redhat.com/errata/RHSA-2015-1176.html
- https://bugzilla.redhat.com/show_bug.cgi?id=1127276
- 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
Frequently Asked Questions
What is the severity of CVE-2014-5075?
CVE-2014-5075 is considered a moderate severity vulnerability due to its potential for MitM attacks.
How do I fix CVE-2014-5075?
To fix CVE-2014-5075, update affected software to version 4.0.2 or later.
Which software is affected by CVE-2014-5075?
CVE-2014-5075 affects the Smack library versions earlier than 4.0.2 and certain versions of Red Hat JBoss Fuse.
What kind of attacks can CVE-2014-5075 lead to?
CVE-2014-5075 can lead to Man-in-the-Middle (MitM) attacks due to lack of hostname verification.
How does CVE-2014-5075 affect SSL connections?
CVE-2014-5075 allows for SSL connections to be compromised by accepting unverified SSL certificates.
- collector/redhat-bugzilla
- alias/CVE-2014-5075
- agent/type
- agent/references
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/author
- agent/severity
- agent/last-modified-date
- agent/description
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- package-manager/redhat
- vendor/redhat
- canonical/red hat jboss fuse
- version/red hat jboss fuse/6.1.0
- vendor/igniterealtime
- canonical/ignite realtime smack api
- version/ignite realtime smack api/4.0.1