Jboss FuseApplication · Redhat
CVE-2014-5075
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Ignite Realtime Smack XMPP API fails to perform hostname verification against the X.509 certificate's CN or subjectAltName fields. When connecting to an XMPP server, the library accepts any valid SSL certificate without validating that it was issued for the intended server, enabling MITM attackers to intercept encrypted communications by presenting a valid certificate for any domain.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Jboss FuseApplication
<= 6.1.0<= 4.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Smack API versionLocate the smack library JAR files in your application's classpath, build dependencies, or lib directory. Check the filename or manifest for the version number (e.g., smack-core-4.0.x.jar)Affected if The version is 4.0.1 or earlier
-
Identify the JBoss Fuse versionRun the 'version' command in the JBoss Fuse console or check the version file in the installation directory (fuse.version or product.conf)Affected if The version is 6.1.0 or earlier and includes Smack for XMPP communication
-
Verify if XMPP client connections are in useSearch application code, configuration files, or runtime dependencies for imports or usage of org.jivesoftware.smack classes, or look for XMPP connection configurationsAffected if The application uses Smack to connect to XMPP servers
-
Inspect SSL configuration for hostname verificationReview the SSLContext or TrustManager setup code used for XMPP connections. Check if setHostnameVerifier() is called with a proper HostnameVerifier implementation, or if a custom hostname verification method existsAffected if No hostname verification is explicitly configured, or the default (which performs no verification) is in use
You are affected if you use Smack API version 4.0.1 or earlier (or JBoss Fuse 6.1.0 or earlier) to establish XMPP connections without custom hostname verification enabled in your SSL configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Smack 4.0.2 or later which includes proper hostname verification. For older versions using custom SSLContext, ensure the SSL configuration explicitly enables hostname verification or implement custom hostname verification logic.
Fix this in Jboss Fuse
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-5075 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data