dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2021-20375

MEDIUM · 6.5 CVSS v3.1 Published 2021-10-07
Fix available
A fix is available. Upgrade to after 6.1.0.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 File Gateway 2.2.0.0 through 6.1.1.0 could allow an authenticated user to intercept and replace a message sent by another user due to improper access controls. IBM X-Force ID: 195567.

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:>= 2.2.0.0, <= 5.2.6.5_3>= 6.0.0.0, <= 6.0.3.4>= 6.1.0.0, <= 6.1.0.1

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

6.1.1.0 or later (or latest available release for your version branch with the security fix)

  1. Check current IBM Sterling B2B Integrator version by logging into the console or checking the installation properties
  2. Review the IBM Support Page https://www.ibm.com/support/pages/node/6496803 for the specific interim fix (iFix) applicable to your version branch
  3. For version 5.2.x: Apply the iFix for 5.2.6.5_3 or upgrade to 5.2.6.6 or later
  4. For version 6.0.x: Apply the iFix for 6.0.3.4 or upgrade to 6.0.3.5 or later
  5. For version 6.1.x: Apply the iFix for 6.1.0.1 or upgrade to 6.1.1.0 or later (which is noted as the fixed release in the official description)
  6. After applying the fix, verify by testing that users cannot intercept/modify messages they did not originate
  7. Consult IBM Sterling B2B Integrator documentation for proper restart procedures after patch application
Caveat Review IBM release notes for your target version to check for any compatibility or configuration changes; test in non-production environment first

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-2021-20375 — 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-20375 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