dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2024-31913

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-06
Fix available
A fix is available. Upgrade to after 6.2.0.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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.1.2.5 and 6.2.0.0 through 6.2.0.2 is vulnerable to stored cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

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 Standard Edition versions 6.0.0.0-6.1.2.5 and 6.2.0.0-6.2.0.2 contains a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can embed malicious JavaScript code that persists in the application, executing within other users' trusted sessions and potentially exposing credentials.

MitigationApply the IBM patch when released. In the interim, implement web application firewall (WAF) rules to filter malicious script payloads and restrict administrative access to trusted users only.

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.5>= 6.2.0.0, <= 6.2.0.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Determine installed IBM Sterling B2B Integrator version
    Locate the version file or use the product's built-in version command. Common locations include the installation directory's version.properties or version.txt file, or execute 'productInfo.bat' or 'productInfo.sh' from the installation bin folder.
    Affected if The installed version falls within 6.0.0.0-6.1.2.5 or 6.2.0.0-6.2.0.2.
  2. Verify Web UI component is enabled
    Check the Web UI configuration files (typically in the install_dir/si directory) or inspect running services. Look for 'webui' or 'portal' related configuration entries in si.properties or si_config.xml.
    Affected if The Web UI component is enabled and accessible to users.
  3. Confirm Web UI is network-accessible
    Test connectivity to the Web UI port (default 8443 or 443) using a browser or curl command: curl -k https://<hostname>:<port>/ Sterling/translate. Verify the login page loads.
    Affected if The Web UI is reachable over the network from untrusted segments.
  4. Inspect Web UI user input fields for persisted scripts
    Log into the Web UI as an administrator and manually review fields that accept user input such as user profiles, notification templates, partner profiles, and custom naming fields. Check for unsanitized HTML or script tags stored in the database.
    Affected if Malicious JavaScript code is stored in any Web UI input field and executes when viewed by other users.
  5. Review Web UI audit and access logs
    Examine Web UI logs in the install_dir/logs directory for unusual patterns such as <script> tags, javascript: URIs, or event handler attributes (onload, onerror, onclick) in logged requests.
    Affected if Logs contain evidence of XSS payloads being submitted to the Web UI.

The environment is affected if the installed IBM Sterling B2B Integrator version is 6.0.0.0-6.1.2.5 or 6.2.0.0-6.2.0.2 AND the Web UI component is enabled and 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 a release after 6.2.0.2
Interim mitigation

Apply the IBM patch when released. In the interim, implement web application firewall (WAF) rules to filter malicious script payloads and restrict administrative access to trusted users only.

Recommended fix Moderate confidence

IBM Sterling B2B Integrator 6.1.3.0 or later, or 6.2.1.0 or later (verify exact fixed version in IBM security bulletin)

  1. 1. Review IBM's official security bulletin for CVE-2024-31913 to obtain the specific patch or fixed version number.
  2. 2. Download the appropriate IBM Sterling B2B Integrator fix from IBM Fix Central (https://www.ibm.com/support/fixcentral/).
  3. 3. Schedule a maintenance window and create a full backup of the current Sterling B2B Integrator installation and database.
  4. 4. Test the upgrade in a non-production environment first to validate compatibility with your existing configurations and integrations.
  5. 5. Apply the security fix or upgrade to a version beyond 6.1.2.5 (such as 6.1.3.0 or later) or beyond 6.2.0.2 (such as 6.2.1.0 or later).
  6. 6. After applying the fix, clear browser caches and verify the Web UI loads correctly.
  7. 7. Test that the XSS vulnerability is remediated by attempting to inject a harmless script in the affected UI fields.
  8. 8. Monitor system logs for any errors during and after the upgrade process.
Caveat Standard IBM upgrade precautions apply - review migration guides and test integrations in staging before production deployment

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 / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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