dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2025-36002

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-16
Fix available
A fix is available. Upgrade to 6.2.0.5_1 or later.
See remediation →
57/100
Remediation priority · Elevated
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 6.2.0.0 through 6.2.0.5, and 6.2.1.0 and IBM Sterling File Gateway 6.2.0.0 through 6.2.0.5, and 6.2.1.0 stores user credentials in configuration files which can be read by a local 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 · high confidence

IBM Sterling B2B Integrator and Sterling File Gateway versions 6.2.0.0-6.2.0.5 and 6.2.1.0 store user credentials in plaintext within configuration files. A local user with filesystem access can read these configuration files to obtain valid credentials.

MitigationRestrict filesystem permissions on configuration files to limit local user access, and implement encrypted credential storage or external secrets management. Contact IBM for available patches.

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.2.0.0, < 6.2.0.5_1= 6.2.1.0
Sterling File GatewayApplication
Affected:>= 6.2.0.0, < 6.2.0.5_1= 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/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 and inspect the installed version of IBM Sterling B2B Integrator using product-specific version detection methods or check product release documentation
    Affected if The installed version is 6.2.0.0 through 6.2.0.5, or exactly 6.2.1.0
  2. Check Sterling File Gateway version
    Locate and inspect the installed version of Sterling File Gateway using product-specific version detection methods or check product release documentation
    Affected if The installed version is 6.2.0.0 through 6.2.0.5, or exactly 6.2.1.0
  3. Identify credential storage configuration files
    Locate configuration files within the product installation directory that store user credentials for authentication purposes
    Affected if Configuration files containing user credentials exist in the product installation directory
  4. Inspect credentials for plaintext storage
    Open and examine the identified credential storage configuration files to determine if credentials are stored in plaintext rather than encrypted or hashed
    Affected if Credentials are stored in plaintext within configuration files that are readable by local users with filesystem access

A system is affected if it runs IBM Sterling B2B Integrator or Sterling File Gateway versions 6.2.0.0-6.2.0.5 or 6.2.1.0 and has configuration files containing plaintext user credentials accessible to local 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.2.0.5_1 or later
Fixed in 6.2.0.5_1
Interim mitigation

Restrict filesystem permissions on configuration files to limit local user access, and implement encrypted credential storage or external secrets management. Contact IBM for available patches.

Recommended fix Moderate confidence

6.2.0.5_1 or later (excluding 6.2.1.0, recommend latest 6.2.x stable release)

  1. Verify current IBM Sterling B2B Integrator or Sterling File Gateway version by checking the system configuration or using the version check utility
  2. Review IBM's official fix documentation at www.ibm.com for complete upgrade instructions
  3. Ensure a complete backup of the current configuration, including all configuration files that may contain credentials
  4. Schedule a maintenance window for the upgrade process
  5. Download the fixed version (6.2.0.5_1 or later, excluding 6.2.1.0 which remains vulnerable) from IBM Fix Central or your authorized IBM distribution channel
  6. Follow IBM's standard upgrade procedure for Sterling B2B Integrator/Sterling File Gateway
  7. After upgrade, verify that the credentials are no longer stored in plaintext in configuration files
  8. Validate that all services start correctly and the application functions as expected
Caveat Review IBM release notes for the target version to check for any breaking changes or required migration steps specific to your configuration

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

Fix this in Sterling B2b Integrator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,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 $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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