VulnerabilityPublished 19 Aug 2025

CVE-2025-2988: IBM Sterling B2B Integrator · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects IBM Sterling B2B IntegratorSource CVE Database V5

Not known to be exploited · CVSS 2.7 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

2.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBM Sterling B2B Integrator	Affected =6.0.0.0 =6.2.0.0 =6.2.1.0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately review and restrict administrative access to IBM Sterling B2B Integrator systems, ensuring that only necessary personnel have high privilege accounts. 2) Monitor and audit access logs for unusual or unauthorized attempts to access sensitive system information. 3) Implement network segmentation and firewall rules to limit exposure of the IBM Sterling B2B Integrator servers to trusted networks and users only. 4) Apply the principle of least privilege in user role assignments within the platform. 5) Stay alert for official patches or updates from IBM addressing CVE-2025-2988 and apply them promptly once available. 6) Conduct regular vulnerability assessments and penetration testing focusing on information disclosure vectors. 7) Educate administrators about the risks of information disclosure and the importance of secure configuration management. These steps go beyond generic advice by emphasizing access control tightening, monitoring, and proactive vulnerability management tailored to the affected product and environment.

Description

IBM Sterling B2B Integrator and IBM Sterling File Gateway 6.0.0.0 through 6.1.2.7, 6.2.0.0 through 6.2.0.4, and 6.2.1.0 could disclose sensitive server information to an unauthorized user that could aid in further attacks against the system.

Impact

For European organizations, the exposure of sensitive system information in IBM Sterling B2B Integrator could have several implications. Although the severity is low, the disclosed information might include configuration details, system architecture, or other metadata that could facilitate reconnaissance by attackers. This could lead to more sophisticated attacks such as privilege escalation, targeted phishing, or exploitation of other vulnerabilities. Since IBM Sterling B2B Integrator is often used in critical supply chain and financial transaction environments, any compromise could disrupt business operations or lead to data breaches. European organizations handling sensitive or regulated data (e.g., under GDPR) must consider the risk of indirect impact through chained attacks. The requirement for high privileges to exploit this vulnerability somewhat limits the risk to insider threats or attackers who have already gained elevated access, but it still warrants attention in environments where multiple users have administrative access.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7242391 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Aug 2025, 19:48 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats