dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2025-14483

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 6.1.2.8 / 6.2.0.5_2 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.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1, and 6.2.2.0 could disclose sensitive host information to authenticated users in responses that could be used 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 IBM Sterling File Gateway contain an information disclosure vulnerability where authenticated users can receive sensitive host information in system responses. This host information could be leveraged by attackers for reconnaissance to plan further attacks against the system.

MitigationApply IBM's security patches for this vulnerability to the affected product versions. Restrict access to the affected interfaces to only necessary authenticated users as a compensating control until patching is complete.

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.1.0.0, < 6.1.2.8>= 6.2.0.0, < 6.2.0.5_2>= 6.2.1.0, < 6.2.1.1_2= 6.2.2.0
Sterling File GatewayApplication
Affected:>= 6.1.0.0, < 6.1.2.8>= 6.2.0.0, < 6.2.0.5_2>= 6.2.1.0, < 6.2.1.1_2= 6.2.2.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. Identify installed IBM Sterling product
    Check the installed product by reviewing the installation directory or running: ls /opt/ibm/Sterling* or check the application name in the web interface
    Affected if Either IBM Sterling B2B Integrator or IBM Sterling File Gateway is installed
  2. Determine product version
    Check the version file typically located in the installation directory, such as /opt/ibm/SB2BI/version.txt or /opt/ibm/SFG/version.txt, or access the version through the admin console under system information
    Affected if The version falls within the affected ranges: 6.1.0.0 to 6.1.2.7, 6.2.0.0 to 6.2.0.5_1, 6.2.1.0 to 6.2.1.1_1, or exactly 6.2.2.0
  3. Verify authenticated user access is enabled
    Confirm the system has user authentication enabled and users can log in, as the vulnerability affects authenticated users receiving host information in responses
    Affected if Authenticated users can access the system (this is the default configuration)
  4. Inspect API or UI responses for host information
    As an authenticated user, make requests to common endpoints and inspect responses for sensitive host information such as internal IP addresses, hostnames, or server paths that should not be disclosed
    Affected if Responses to authenticated users contain internal host details that should not be exposed

The environment is affected if IBM Sterling B2B Integrator or Sterling File Gateway is running a version within the listed affected ranges and authenticated users can access the system.

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.8 / 6.2.0.5_2 / 6.2.1.1_2 or later
Fixed in 6.1.2.86.2.0.5_26.2.1.1_2
Interim mitigation

Apply IBM's security patches for this vulnerability to the affected product versions. Restrict access to the affected interfaces to only necessary authenticated users as a compensating control until patching is complete.

Recommended fix Moderate confidence

6.1.2.8 (for 6.1.x), 6.2.0.5_2 (for 6.2.0.x), 6.2.1.1_2 (for 6.2.1.x), or latest release above 6.2.2.0

  1. Identify the specific Sterling B2B Integrator or Sterling File Gateway version currently deployed using the system administration console or version check utility
  2. For version 6.1.0.0 through 6.1.2.7_2: upgrade to version 6.1.2.8 or later
  3. For version 6.2.0.0 through 6.2.0.5_1: upgrade to version 6.2.0.5_2 or later
  4. For version 6.2.1.0 through 6.2.1.1_1: upgrade to version 6.2.1.1_2 or later
  5. For version 6.2.2.0: upgrade to the next available maintenance release (version higher than 6.2.2.0)
  6. After upgrade, verify the fix by testing that sensitive host information is no longer exposed in authenticated user responses
  7. Consult IBM documentation for any specific post-upgrade configuration requirements
Caveat Review IBM release notes for potential compatibility impacts; test in non-production environment first

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-14483 — 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-14483 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