dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2022-22371

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-05
Fix available
A fix is available. Upgrade to after 6.1.1.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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 does not invalidate session after a password change which could allow an authenticated user to impersonate another user on the system. IBM X-Force ID: 221195.

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

A detailed technical summary for this CVE is being prepared.

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.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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.1.1.1
Vendor patch www.ibm.com →
Recommended fix Moderate confidence

IBM Sterling B2B Integrator 6.1.2.1 or later (the description indicates versions through 6.1.2.1 are affected; upgrade to a version beyond 6.1.2.1 as specified in IBM's patch documentation)

  1. 1. Review the IBM support page for this vulnerability at https://www.ibm.com/support/pages/node/6852461 for the specific patch or fixed version.
  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. Plan the upgrade during a maintenance window as session handling changes may affect active users.
  4. 4. Back up the current IBM Sterling B2B Integrator configuration and database before upgrading.
  5. 5. Apply the IBM fix/patch or upgrade to the fixed version as specified in the IBM support documentation.
  6. 6. After upgrading, verify that user sessions are properly invalidated when passwords are changed.
  7. 7. Inform users that they will need to re-authenticate after the upgrade due to the session fix.
Caveat Minor - users will need to re-authenticate after password changes; test thoroughly in non-production environment before deploying

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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