CVE-2014-5075
published 2014-10-25CVE-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…
PriorityP428medium6.8CVSS 2.0
AVNACMAuNCPIPAP
EPSS
0.92%
56.2th percentile
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.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| igniterealtime | smack_api | <= 4.0.1 | — |
| redhat | jboss_fuse | <= 6.1.0 | — |
CVSS provenance
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
vendor_redhat6.8MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
smack: MitM vulnerability
vendor_redhat·2014-08-05·CVSS 6.8
CVE-2014-5075 [MEDIUM] smack: MitM vulnerability
smack: MitM vulnerability
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.
It was found that SSLSocket in Smack did not perform hostname verification. An attacker could redirect traffic between an application and an XMPP server by providing a valid certificate for a domain under the attacker's control.
Package: smack (Red Hat JBoss BRMS 5) - Will not fix
GHSA
GHSA-pxxv-xr7h-7624: The Ignite Realtime Smack XMPP API 4
ghsa_unreviewed·2022-05-17
CVE-2014-5075 [MEDIUM] GHSA-pxxv-xr7h-7624: The Ignite Realtime Smack XMPP API 4
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2014-5075 smack: MitM vulnerability
bugzilla·2014-08-06·CVSS 5.8
CVE-2014-5075 [MEDIUM] CVE-2014-5075 smack: MitM vulnerability
CVE-2014-5075 smack: MitM vulnerability
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 nameConstr
Bugzilla
CVE-2014-5075 smack: MitM vulnerability [fedora-all]
bugzilla·2014-08-06·CVSS 6.8
CVE-2014-5075 [MEDIUM] CVE-2014-5075 smack: MitM vulnerability [fedora-all]
CVE-2014-5075 smack: MitM vulnerability [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tr
http://op-co.de/CVE-2014-5075.htmlhttp://rhn.redhat.com/errata/RHSA-2015-1176.htmlhttp://secunia.com/advisories/59915http://www.securityfocus.com/bid/69064http://op-co.de/CVE-2014-5075.htmlhttp://rhn.redhat.com/errata/RHSA-2015-1176.htmlhttp://secunia.com/advisories/59915http://www.securityfocus.com/bid/69064
2014-10-25
Published