dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2022-22352

MEDIUM · 5.4 CVSS v3.1 Published 2023-01-04
Fix available
A fix is available. Upgrade to 6.0.3.7 / 6.1.0.6 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.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: 220398.

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 through 6.1.2.1 contains a stored cross-site scripting (XSS) vulnerability in its Web UI. An authenticated attacker can embed arbitrary JavaScript code into the web interface, which executes in the browsers of other users viewing the affected content, potentially exposing credentials or session tokens within a trusted session.

MitigationApply the IBM security patch for CVE-2022-22352 to upgrade to a fixed version. If immediate patching is not feasible, implement input validation and output encoding on all user-supplied data in the Web UI, and consider restricting or monitoring administrative access until the patch can be deployed.

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.7>= 6.1.0.0, < 6.1.0.6>= 6.1.1.0, < 6.1.1.2= 6.1.2.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
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 version of IBM Sterling B2B Integrator
    Locate the product version through the administration console, installation directory version file, or by querying the system via command line (e.g., 'productVersion' command or checking release notes in the installation folder).
    Affected if The version displayed is 6.0.0.0 through 6.0.3.6, 6.1.0.0 through 6.1.0.5, 6.1.1.0 through 6.1.1.1, or exactly 6.1.2.0.
  2. Confirm Web UI component is enabled and accessible
    Verify that the Sterling B2B Integrator web-based user interface (typically accessed via browser on ports 8443, 443, or 8080) is currently active and reachable on the network.
    Affected if The Web UI is exposed and users can authenticate to access the interface.
  3. Review recent security patches applied to the system
    Check the system's patch history or IBM fix pack inventory to determine if any security patches have been installed since the initial version was deployed.
    Affected if No security patches addressing CVE-2022-22352 have been applied and the version falls within affected ranges.
  4. Identify the deployment type
    Determine if the installation is Standard Edition (the affected product) by checking the product edition through the license or system information panel.
    Affected if The installation is Standard Edition and the version matches the affected ranges.

The environment is affected if IBM Sterling B2B Integrator Standard Edition is running a version within 6.0.0.0 to 6.0.3.6, 6.1.0.0 to 6.1.0.5, 6.1.1.0 to 6.1.1.1, or exactly 6.1.2.0, and the Web UI is 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.7 / 6.1.0.6 / 6.1.1.2 or later
Fixed in 6.0.3.76.1.0.66.1.1.2
Interim mitigation

Apply the IBM security patch for CVE-2022-22352 to upgrade to a fixed version. If immediate patching is not feasible, implement input validation and output encoding on all user-supplied data in the Web UI, and consider restricting or monitoring administrative access until the patch can be deployed.

Recommended fix High confidence

Upgrade to 6.0.3.7 (for 6.0.x branch), 6.1.0.6 (for 6.1.0.x branch), 6.1.1.2 (for 6.1.1.x branch), or 6.1.2.1 or later (for 6.1.2.x branch)

  1. 1. Identify the currently installed IBM Sterling B2B Integrator version using the system administration console or version check utility.
  2. 2. Determine the appropriate upgrade path based on your current version branch (6.0.x, 6.1.0.x, 6.1.1.x, or 6.1.2.x).
  3. 3. Download the corresponding fixed release from IBM Fix Central or your authorized IBM support portal.
  4. 4. Back up the existing Sterling B2B Integrator database, configuration files, and customizations.
  5. 5. Stop all Sterling B2B Integrator services and related processes.
  6. 6. Install the upgrade following IBM's standard upgrade procedures documented in the Installation Guide.
  7. 7. After installation, verify the fix by logging into the Web UI and confirming the XSS vulnerability is no longer exploitable.
  8. 8. Restart all Sterling B2B Integrator services.
Caveat Review IBM's release notes for the target version to check for any compatibility changes, deprecated features, or migration requirements specific to your version branch

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

Fix this in Sterling B2b Integrator Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
36.0 hours of engineering $6,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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