CVE-2014-6170
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 HTTPInput node in IBM WebSphere Message Broker 7.0 before 7.0.0.8 and 8.0 before 8.0.0.6 and IBM Integration Bus 9.0 before 9.0.0.4 allows remote attackers to obtain sensitive information by triggering a SOAP fault.
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 · moderate confidenceThe HTTPInput node in IBM WebSphere Message Broker 7.0 before 7.0.0.8 and 8.0 before 8.0.0.6, and IBM Integration Bus 9.0 before 9.0.0.4 contains an information disclosure vulnerability. Remote attackers can trigger a SOAP fault to cause the node to expose sensitive information that should not be accessible.
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= 9.0= 9.0.0.1= 9.0.0.2= 9.0.0.3= 7.0.= 7.0.0.1= 7.0.0.2= 7.0.0.3= 7.0.0.4= 7.0.0.5= 7.0.0.6= 7.0.0.7= 8.0= 8.0.0.1= 8.0.0.2= 8.0.0.3CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 installed IBM productRun 'mqsilist' command or check installation directory for IBM WebSphere Message Broker or IBM Integration Bus installationsAffected if Product is IBM WebSphere Message Broker or IBM Integration Bus
-
Check product versionRun 'mqsiver' command on the broker or integration node, or check the installed version through the product's about panelAffected if Version is 7.0 before 7.0.0.8, 8.0 before 8.0.0.6, or 9.0 before 9.0.0.4
-
Verify HTTPInput nodes are deployedUse the web admin console or run 'mqsiapplybaroverride' to list deployed resources and check for HTTPInput nodes in any flowsAffected if HTTPInput nodes are deployed in any integration flows
-
Check network exposure of HTTP servicesReview firewall rules and network configuration to determine if the HTTP port used by HTTPInput nodes (default 7080 or custom) is accessible from untrusted networksAffected if HTTPInput endpoint ports are accessible from external or untrusted networks
User is affected if running WebSphere Message Broker 7.0.x before 7.0.0.8, 8.0.x before 8.0.0.6, or Integration Bus 9.0.x before 9.0.0.4 with HTTPInput nodes exposed to the network.
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 dataApply the vendor-supplied patches (WebSphere Message Broker 7.0.0.8, 8.0.0.6, or Integration Bus 9.0.0.4) to resolve the vulnerability. In the interim, restrict network access to the HTTPInput endpoints using firewall rules or network segmentation.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6170 — 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-6170 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