dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2025-2988

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-19
Fix available
A fix is available. Upgrade to 6.1.2.7_1 / 6.2.0.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 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.

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

IBM Sterling B2B Integrator and Sterling File Gateway contain an information disclosure vulnerability allowing unauthorized users to access sensitive server information. The affected versions span multiple release branches (6.0.0.0-6.1.2.7, 6.2.0.0-6.2.0.4, and 6.2.1.0), potentially exposing system configuration details, paths, or internal network information that could aid in reconnaissance for subsequent attacks.

MitigationApply IBM security patches for this vulnerability or upgrade to a patched version beyond 6.2.1.0 as specified in IBM's security bulletin. Restrict network access to administrative interfaces as a compensating control until the patch can be applied.

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
Sterling B2b IntegratorApplication
Affected:>= 6.0.0.0, < 6.1.2.7_1>= 6.2.0.0, < 6.2.0.5= 6.2.1.0
Sterling File GatewayApplication
Affected:>= 6.0.0.0, < 6.1.2.7_1>= 6.2.0.0, < 6.2.0.5= 6.2.1.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Check IBM Sterling B2B Integrator version
    Locate the version file or use the admin console to identify the installed version. Common paths include the installation directory or check the 'About' section in the admin interface.
    Affected if Installed version is 6.0.0.0 through 6.1.2.7, 6.2.0.0 through 6.2.0.4, or exactly 6.2.1.0
  2. Check IBM Sterling File Gateway version
    Locate the version file or use the admin console to identify the installed version. Sterling File Gateway is typically deployed alongside Sterling B2B Integrator.
    Affected if Installed version is 6.0.0.0 through 6.1.2.7, 6.2.0.0 through 6.2.0.4, or exactly 6.2.1.0
  3. Verify network exposure of administrative interfaces
    Determine if the web-based administrative console or REST APIs are accessible from untrusted networks. Check firewall rules and network ACLs restricting access to port 8443 or the configured admin port.
    Affected if Administrative interfaces are accessible from untrusted or public networks without authentication barriers
  4. Test for information disclosure via web endpoints
    Submit unauthenticated requests to common API endpoints and observe whether sensitive system information such as configuration details, file paths, or internal network data is returned in error messages or responses.
    Affected if Unauthenticated requests return system configuration, paths, or network information

You are affected if either Sterling B2B Integrator or Sterling File Gateway is running a version between 6.0.0.0-6.1.2.7, 6.2.0.0-6.2.0.4, or exactly 6.2.1.0 AND the web administrative interface is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 6.1.2.7_1 / 6.2.0.5 or later
Fixed in 6.1.2.7_16.2.0.5
Interim mitigation

Apply IBM security patches for this vulnerability or upgrade to a patched version beyond 6.2.1.0 as specified in IBM's security bulletin. Restrict network access to administrative interfaces as a compensating control until the patch can be applied.

Recommended fix High confidence

IBM Sterling B2B Integrator / Sterling File Gateway 6.1.2.7_1 or later (for 6.0.x-6.1.x), or 6.2.0.5 or later (for 6.2.x)

  1. Identify the current version of IBM Sterling B2B Integrator or Sterling File Gateway installed in the environment
  2. If running version 6.0.0.0 through 6.1.2.7, plan upgrade to version 6.1.2.7_1 or later in the 6.1.x release line
  3. If running version 6.2.0.0 through 6.2.0.4, plan upgrade to version 6.2.0.5 or later in the 6.2.x release line
  4. If running version 6.2.1.0, plan upgrade to the next available maintenance release beyond 6.2.1.0
  5. Review IBM's upgrade documentation and release notes for the target version
  6. Perform a full backup of the current installation, including database and configuration files
  7. Schedule maintenance window for the upgrade process
  8. Execute upgrade following IBM's standard upgrade procedures for Sterling B2B Integrator or Sterling File Gateway

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sterling B2b Integrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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