dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2021-39035

MEDIUM · 5.4 CVSS v3.1 Published 2022-08-16
Fix available
A fix is available. Upgrade to 6.0.3.6 / 6.1.0.5 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.0.3.5, 6.1.0.0 through 6.1.0.4, and 6.1.1.0 through 6.1.1.1 is vulnerable to 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. IBM X-Force ID: 213965.

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 Standard Edition contains a cross-site scripting (XSS) vulnerability in its Web UI. The flaw allows authenticated users to embed arbitrary JavaScript code, potentially altering application functionality and leading to credential disclosure within trusted sessions.

MitigationApply the IBM fix pack for your version (6.0.3.6, 6.1.0.5, or 6.1.1.2) or upgrade to a supported version. If patching is delayed, implement output encoding on Web UI responses and consider restricting UI 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.0.3.6>= 6.1.0.0, < 6.1.0.5>= 6.1.1.0, < 6.1.1.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. Identify the installed IBM Sterling B2B Integrator version
    Locate the version information in the product installation directory, typically found in version or about files within the installation root, or access the Web UI admin console and navigate to the about or system information page
    Affected if The installed version falls within 6.0.0.0 to 6.0.3.5, 6.1.0.0 to 6.1.0.4, or 6.1.1.0 to 6.1.1.1 (any version less than the fixed releases 6.0.3.6, 6.1.0.5, or 6.1.1.2)
  2. Confirm the Web UI component is enabled
    Check if the Sterling B2B Integrator Web UI (typically accessed via HTTP/HTTPS on the configured application port) is accessible and operational
    Affected if The Web UI is accessible and responds to requests, indicating the vulnerable component is exposed
  3. Verify authentication is enabled for the Web UI
    Review the Web UI security configuration to confirm user authentication is configured and active
    Affected if Users can authenticate to the Web UI, which is required for exploiting this XSS vulnerability since it affects authenticated sessions

A user is affected if they have a vulnerable version (less than 6.0.3.6, 6.1.0.5, or 6.1.1.2) of IBM Sterling B2B Integrator running with the Web UI enabled and accessible to authenticated 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.6 / 6.1.0.5 / 6.1.1.2 or later
Fixed in 6.0.3.66.1.0.56.1.1.2
Interim mitigation

Apply the IBM fix pack for your version (6.0.3.6, 6.1.0.5, or 6.1.1.2) or upgrade to a supported version. If patching is delayed, implement output encoding on Web UI responses and consider restricting UI access to trusted users only.

Recommended fix Moderate confidence

IBM Sterling B2B Integrator 6.0.3.6, 6.1.0.5, or 6.1.1.2 (or later respective releases)

  1. Identify the currently installed IBM Sterling B2B Integrator version by checking the system information or release notes
  2. Determine which version branch you are running (6.0.x, 6.1.0.x, or 6.1.1.x)
  3. For version 6.0.x: Upgrade to version 6.0.3.6 or later
  4. For version 6.1.0.x: Upgrade to version 6.1.0.5 or later
  5. For version 6.1.1.x: Upgrade to version 6.1.1.2 or later
  6. After upgrade, verify the XSS vulnerability is resolved by testing that user input is properly sanitized in the Web UI
  7. Review IBM Sterling B2B Integrator documentation for any migration or configuration steps required for the target version
Caveat Review IBM release notes for the target version to check for migration requirements, compatibility considerations, or configuration changes

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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