LiveActive security incident?Get immediate response
CVE Record

CVE-2015-2018: IBM Integration Bus 9 and 10 before 10.0.0.1 and WebSphere Message Broker 7 before 7.0.0.8 and 8 before 8.0...

IBM Integration Bus 9 and 10 before 10.0.0.1 and WebSphere Message Broker 7 before 7.0.0.8 and 8 before 8.0.0.7 do not ensure that the correct security profile is selected, which allows remote authenticated users to obtain sensitive information via unspecified vectors.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw could let an authenticated remote user see sensitive information because IBM broker software may choose the wrong security profile. The public record does not describe the data exposed or the attack path, so urgency depends on whether these legacy products remain in use and who can authenticate to them. Exposure is most likely in organizations still running legacy IBM Integration Bus or WebSphere Message Broker versions. Risk is higher where many users, service accounts, or partner integrations can authenticate remotely to broker interfaces or message-flow management functions. Treat as a targeted legacy-platform exposure. Prioritize remediation if these IBM middleware products still handle sensitive data or are reachable by broad authenticated user populations. Lack of KEV evidence lowers emergency posture, but information disclosure in integration infrastructure can have meaningful business impact. Mitigation focus: Inventory IBM Integration Bus and WebSphere Message Broker deployments and versions.; Upgrade affected releases to IBM-advised fixed levels where applicable.; Review IBM advisory and APAR IT07773 for product-specific remediation guidance..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2015-2018 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.