dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2023-25682

MEDIUM · 5.5 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to 6.0.3.9 / 6.1.2.3 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 Standard Edition 6.0.0.0 through 6.0.3.8 and 6.1.0.0 through 6.1.2.1 stores potentially sensitive information in log files that could be read by a local user. IBM X-Force ID: 247034.

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 stores potentially sensitive information in log files that can be read by local users with filesystem access. This is an information disclosure vulnerability where credentials, tokens, or other sensitive data may be written to application logs.

MitigationConfigure logging to exclude or mask sensitive data fields (credentials, tokens, PII), review existing log files for exposed data and secure/delete as needed, and ensure log files have appropriate filesystem permissions to restrict access.

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.0.3.9>= 6.1.0.0, < 6.1.2.3

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. Identify IBM Sterling B2B Integrator installed version
    Locate and read the version file or use the product's version command (e.g., productVersion script in the installation directory, or check installation metadata)
    Affected if The installed version falls within 6.0.0.0 through 6.0.3.8 OR 6.1.0.0 through 6.1.2.2 (the affected ranges)
  2. Confirm the installation directory structure
    Identify the base installation path for IBM Sterling B2B Integrator (commonly under /opt/ibm or C:\ibm on Windows)
    Affected if The product is installed and you can access the installation directory
  3. Locate application log files
    Navigate to the logs or output directory within the installation path (typical paths include logs/, output/, or data/ directories) and list all log files
    Affected if Log files exist in the installation directory
  4. Inspect log files for sensitive data
    Search within log files for patterns indicating sensitive information: look for strings like 'password', 'token', 'credential', 'secret', 'apiKey', 'basic auth', or base64-encoded strings that may represent credentials
    Affected if Log files contain plaintext or weakly encoded credentials, tokens, API keys, or other sensitive data that should not be exposed
  5. Check filesystem permissions on log files
    Review file permissions on the log directory and individual log files to determine if unprivileged local users can read them
    Affected if Log files are readable by users other than the application owner or administrator

You are affected if the installed IBM Sterling B2B Integrator version is 6.0.0.0 through 6.0.3.8 or 6.1.0.0 through 6.1.2.2 AND your log files contain exposed sensitive data that is 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.0.3.9 / 6.1.2.3 or later
Fixed in 6.0.3.96.1.2.3
Interim mitigation

Configure logging to exclude or mask sensitive data fields (credentials, tokens, PII), review existing log files for exposed data and secure/delete as needed, and ensure log files have appropriate filesystem permissions to restrict access.

Recommended fix High confidence

6.0.3.9 (for 6.0.x branch) or 6.1.2.3 (for 6.1.x branch)

  1. Identify the currently installed IBM Sterling B2B Integrator version by checking the system or installation documentation
  2. If running version 6.0.0.0 through 6.0.3.8, plan upgrade to version 6.0.3.9 or later
  3. If running version 6.1.0.0 through 6.1.2.1, plan upgrade to version 6.1.2.3 or later
  4. Review IBM's official upgrade documentation and release notes for Sterling B2B Integrator
  5. Perform a backup of the current system and configuration
  6. Execute the upgrade following IBM's recommended upgrade procedure
  7. After upgrade, verify the version number matches the target fixed release
  8. Confirm the vulnerability is resolved by reviewing release notes or testing
Caveat Standard upgrade risks apply - test in non-production environment first, review migration guides for compatibility with custom 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-2023-25682 — 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-2023-25682 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