dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2024-47103

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-31
Fix available
A fix is available. Upgrade to after 6.2.0.3 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 6.0.0.0 through 6.1.2.5 and 6.2.0.0 through 6.2.0.3 Standard Edition is vulnerable to cross-site scripting. This vulnerability allows a privileged user 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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability in IBM Sterling B2B Integrator's Web UI allows a privileged user to inject malicious JavaScript that executes in other users' sessions, potentially exposing credentials within trusted sessions.

MitigationImplement input validation and output encoding on all user-supplied content in the Web UI; deploy Content Security Policy (CSP) headers to restrict script execution.

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.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
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. Identify installed IBM Sterling B2B Integrator version
    Run the command 'ls -la' in the installation directory or check the version file typically found in the product's bin or properties directory. Alternatively, access the Web UI login page and check any version information displayed, or query the system via administrative APIs if available.
    Affected if The installed version falls within 6.0.0.0 through 6.1.2.5 OR 6.2.0.0 through 6.2.0.3.
  2. Confirm Web UI component is enabled and accessible
    Verify the IBM Sterling B2B Integrator Web UI (typically accessed via HTTP/HTTPS on ports 8443 or similar) is reachable. Check the application server configuration to confirm the Web UI servlets and handlers are deployed and running.
    Affected if The Web UI is accessible over the network and users can authenticate to it.
  3. Review Web UI input fields for stored content
    Log into the Web UI as a privileged user and examine fields that accept user-supplied content, such as user profiles, custom templates, notification settings, or business process configuration screens. Inspect the HTML source of stored values to see if raw input is rendered without encoding.
    Affected if User-supplied content in Web UI fields is rendered with unencoded HTML or JavaScript syntax visible in the page source.
  4. Examine server logs for XSS indicators
    Search the Web UI and application server logs (typically in the 'logs' directory of the installation) for patterns like '<script', 'javascript:', 'onerror=', 'onload=', or other JavaScript event handlers that may indicate XSS injection attempts or successful stored XSS payloads.
    Affected if Logs contain patterns matching script injection attempts or stored XSS payloads in Web UI contexts.

Your environment is affected if the installed IBM Sterling B2B Integrator version is within 6.0.0.0-6.1.2.5 or 6.2.0.0-6.2.0.3 and the Web UI is accessible to 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.

From vendor data
Upgrade available Upgrade to a release after 6.2.0.3
Interim mitigation

Implement input validation and output encoding on all user-supplied content in the Web UI; deploy Content Security Policy (CSP) headers to restrict script execution.

Fix this in Sterling B2b Integrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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