dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2025-36112

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-24
Fix available
A fix is available. Upgrade to 6.1.2.7_2 / 6.2.0.5_1 or later.
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 Sterling B2B Integrator and IBM Sterling File Gateway 6.0.0.0 through 6.1.2.7 and 6.2.0.0 through 6.2.0.5 and 6.2.1.1 could reveal sensitive server IP configuration information to an unauthorized user.

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 unauthenticated users to obtain sensitive server IP configuration details. This is a network-exploitable issue with no authentication required, exposing internal network topology information.

MitigationApply the IBM-provided security patches or upgrades to the affected versions (6.0.0.0-6.1.2.7, 6.2.0.0-6.2.0.5, 6.2.1.1). Restrict network access to administrative interfaces 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
Sterling B2b IntegratorApplication
Affected:>= 6.0.0.0, < 6.1.2.7_2>= 6.2.0.0, < 6.2.0.5_1= 6.2.1.1
Sterling File GatewayApplication
Affected:>= 6.0.0.0, < 6.1.2.7_2>= 6.2.0.0, < 6.2.0.5_1= 6.2.1.1

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.1/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 version of IBM Sterling B2B Integrator
    Locate the product version information in the system documentation, installation directory, or admin console. Typical locations include the system information panel or version.txt file in the installation directory.
    Affected if The installed version is >= 6.0.0.0 and < 6.1.2.7_2, or >= 6.2.0.0 and < 6.2.0.5_1, or exactly 6.2.1.1
  2. Identify the installed version of IBM Sterling File Gateway
    Locate the product version information in the system documentation, installation directory, or admin console. This may be accessible through the same methods as the B2B Integrator or within the Gateway-specific administration interface.
    Affected if The installed version is >= 6.0.0.0 and < 6.1.2.7_2, or >= 6.2.0.0 and < 6.2.0.5_1, or exactly 6.2.1.1
  3. Determine if administrative interfaces are network-accessible
    Review firewall rules, network configurations, and access control lists to check whether the IBM Sterling admin ports or web interfaces are exposed to untrusted networks or the internet.
    Affected if The admin interface is reachable from untrusted networks without authentication required for access
  4. Verify if unauthenticated endpoints are reachable
    Test connectivity to common Sterling administrative endpoints using a web browser or curl command from an untrusted network location to confirm whether unauthenticated access is possible.
    Affected if Unauthenticated users can access server IP configuration details or internal network topology information through exposed endpoints

You are affected if either IBM Sterling B2B Integrator or Sterling File Gateway is running a version within the affected ranges AND the administrative interface is network-accessible to unauthenticated users.

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_2 / 6.2.0.5_1 or later
Fixed in 6.1.2.7_26.2.0.5_1
Interim mitigation

Apply the IBM-provided security patches or upgrades to the affected versions (6.0.0.0-6.1.2.7, 6.2.0.0-6.2.0.5, 6.2.1.1). Restrict network access to administrative interfaces as an interim control.

Recommended fix High confidence

6.1.2.7_2 or 6.2.0.5_1 (depending on current branch)

  1. 1. Identify the current version of IBM Sterling B2B Integrator or Sterling File Gateway by checking the product dashboard or version information.
  2. 2. Determine which version branch you are currently on (6.0.x-6.1.x or 6.2.x).
  3. 3. For systems on version 6.0.0.0 through 6.1.2.7: Plan upgrade to version 6.1.2.7_2 or later.
  4. 4. For systems on version 6.2.0.0 through 6.2.0.5: Plan upgrade to version 6.2.0.5_1 or later.
  5. 5. For systems on version 6.2.1.1: Upgrade to the latest available version that includes the security fix (6.2.0.5_1 or newer).
  6. 6. Review IBM's upgrade documentation and release notes for the target version before proceeding.
  7. 7. Perform a full backup of the current system and configurations.
  8. 8. Test the upgrade in a non-production environment first.
Caveat Review IBM release notes for your specific version path; some upgrades may require intermediate steps or have compatibility considerations with existing integrations.

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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