dbcve.org
Integration BusApplication · Ibm

CVE-2016-2961

MEDIUM · 5.3 CVSS v3.0 Published 2016-07-02
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
The integration server in IBM Integration Bus 9 before 9.0.0.6 and 10 before 10.0.0.5 and WebSphere Message Broker 8 before 8.0.0.8 allows remote attackers to obtain sensitive Tomcat version information by sending a malformed POST request and then reading the Java stack trace.

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 confidence

The IBM Integration Bus and WebSphere Message Broker integration servers expose Tomcat version information through verbose Java stack traces when malformed POST requests are received. An unauthenticated remote attacker can send specially crafted requests to trigger error pages that reveal the underlying Tomcat server version in the response.

MitigationApply the vendor security patches: IBM Integration Bus 9.0.0.6+, 10.0.0.5+, and WebSphere Message Broker 8.0.0.8+ to prevent version disclosure.

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= 9.0.0.3= 9.0.0.4= 9.0.0.5= 10.0= 10.0.0.1= 10.0.0.2= 10.0.0.3= 10.0.0.4
Websphere Message BrokerApplication
Affected:= 8.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.0.4= 8.0.0.5= 8.0.0.6= 8.0.0.7

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 the installed product and version
    Determine whether IBM Integration Bus or WebSphere Message Broker is installed and note its exact version number by checking the product documentation or using the appropriate version command for the system
    Affected if The installed version matches one of the affected versions: 9.0, 9.0.0.1-9.0.0.5, 10.0, 10.0.0.1-10.0.0.4 for Integration Bus; or 8.0.0.1-8.0.0.7 for WebSphere Message Broker
  2. Locate the integration server HTTP listener
    Identify the HTTP port and endpoint used by the integration server for receiving web requests, typically configured in the integration node or integration server properties
    Affected if The integration server HTTP listener is accessible over the network and accepts POST requests
  3. Send a malformed POST request to trigger an error
    Send a specially crafted or malformed POST request to any accessible HTTP endpoint of the integration server, such as a simple flow or REST API endpoint, ensuring the request triggers an error condition
    Affected if The server processes the request and returns an error response page rather than rejecting it at the network level
  4. Inspect the error response for Tomcat version disclosure
    Examine the HTTP response body from the malformed request for any mention of Tomcat, Apache, or version numbers in stack traces, error messages, or server information headers
    Affected if The error response contains Tomcat version information such as 'Apache Tomcat', version numbers like 7.x or 8.x, or detailed Java stack traces that reveal the underlying servlet container

A user is affected if they are running an affected version of IBM Integration Bus or WebSphere Message Broker AND their integration server HTTP endpoints are exposed such that malformed POST requests trigger verbose error pages revealing Tomcat version details.

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 security patches: IBM Integration Bus 9.0.0.6+, 10.0.0.5+, and WebSphere Message Broker 8.0.0.8+ to prevent version disclosure.

Fix this in Integration Bus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-2961 — 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-2016-2961 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