dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2022-22337

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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.1.2.1 could disclose sensitive information to an authenticated user. IBM X-Force ID: 219507.

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 versions 6.0.0.0 through 6.1.2.1 contains an information disclosure vulnerability where an authenticated user could gain access to sensitive information beyond their authorized scope. The vulnerability requires authentication but could expose confidential data to unauthorized users.

MitigationApply the vendor-supplied security patch or upgrade to a fixed version as specified in IBM's security bulletin. Verify user access controls and audit existing user permissions until the patch can be applied.

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.2.1= 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/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 version
    Locate the installed version of IBM Sterling B2B Integrator. This is typically visible in the product's admin console, or can be retrieved via system information pages or installation logs. Common locations include the release information in the dashboard or about section of the web interface.
    Affected if The installed version is 6.0.0.0 through 6.0.3.6, OR 6.1.0.0 through 6.1.0.5, OR 6.1.1.0 through 6.1.2.0 (including 6.1.2.0).
  2. Confirm version is within affected range
    Compare your identified version number against the affected ranges: versions 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.2.0.
    Affected if The version matches any of the affected ranges listed above.
  3. Verify patch status
    Check if the installed version has been patched. Fixed versions are 6.0.3.7 and later, 6.1.0.6 and later, and 6.1.2.1 and later. Contact IBM support or check release notes to confirm patch status.
    Affected if The version is below the fixed releases and no security patch has been applied.

You are affected if your IBM Sterling B2B Integrator version falls within 6.0.0.0-6.0.3.6, 6.1.0.0-6.1.0.5, or 6.1.1.0-6.1.2.0 and no vendor patch has been applied.

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.2.1 or later
Fixed in 6.0.3.76.1.0.66.1.2.1
Interim mitigation

Apply the vendor-supplied security patch or upgrade to a fixed version as specified in IBM's security bulletin. Verify user access controls and audit existing user permissions until the patch can be applied.

Recommended fix High confidence

IBM Sterling B2B Integrator 6.1.2.1 or later (or 6.0.3.7+ for 6.0.x branch, 6.1.0.6+ for 6.1.0.x branch)

  1. 1. Back up the current IBM Sterling B2B Integrator configuration and database.
  2. 2. Review IBM Sterling B2B Integrator upgrade documentation for your current version.
  3. 3. Download IBM Sterling B2B Integrator version 6.1.2.1 or later from IBM Fix Central.
  4. 4. Stop all Sterling B2B Integrator services before upgrading.
  5. 5. Run the installer/upgrader following IBM's standard upgrade procedures.
  6. 6. After upgrade, verify that all services start correctly.
  7. 7. Test that the vulnerability is no longer present by confirming authenticated users can no longer access unauthorized sensitive information.
Caveat Review IBM release notes for potential configuration or compatibility changes between your current version and the target version

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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