dbcve.org
Integration BusApplication · Ibm

CVE-2015-7399

MEDIUM · 5.3 CVSS v3.0 Published 2016-01-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
IBM WebSphere Message Broker 7 before 7.0.0.8 and 8 before 8.0.0.6 and IBM Integration Bus 9 before 9.0.0.3 and 10 before 10.0.0.0 allow remote attackers to obtain sensitive information about the HTTP server via unspecified vectors.

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 confidence

This is an information disclosure vulnerability in IBM WebSphere Message Broker and IBM Integration Bus HTTP server components. Remote attackers can obtain sensitive information about the HTTP server via unspecified vectors. The vulnerability affects versions prior to 7.0.0.8, 8.0.0.6, 9.0.0.3, and 10.0.0.0.

MitigationApply the vendor-supplied patches (7.0.0.8, 8.0.0.6, 9.0.0.3, 10.0.0.0) or upgrade to the patched versions. Restrict network access to the HTTP server ports as an interim control.

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
Integration BusApplication
Affected:= 9.0= 9.0.0.1= 9.0.0.2= 10.0
Websphere Message BrokerApplication
Affected:= 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.3

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product
    Run 'mqsilist' command or check installation directory for IBM Integration Bus or WebSphere Message Broker binaries
    Affected if Product is IBM Integration Bus or WebSphere Message Broker
  2. Determine product version
    Run 'mqsilist -v' or check version info in installation path (typically under /opt/ibm/ or C:\Program Files\ibm\)
    Affected if Version is 7.0.0.0-7.0.0.7, 8.0.0.0-8.0.0.3, 9.0.0.0-9.0.0.2, or 10.0.0.0 (pre-patch)
  3. Verify HTTP server component is in use
    Check for HTTP listener ports (typically 7080, 8080, or configured ports) in broker configuration or running processes with 'mqsilist' output
    Affected if HTTP server component is configured and running

User is affected if running IBM Integration Bus (9.0-9.0.0.2 or 10.0) or WebSphere Message Broker (7.0.0.0-7.0.0.7 or 8.0.0.0-8.0.0.3) with HTTP server component enabled and version is below the fixed releases (7.0.0.8, 8.0.0.6, 9.0.0.3, 10.0.0.0).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches (7.0.0.8, 8.0.0.6, 9.0.0.3, 10.0.0.0) or upgrade to the patched versions. Restrict network access to the HTTP server ports as an interim control.

Fix this in Integration Bus Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7399 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-7399 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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