dbcve.org
Sterling B2b IntegratorApplication · Ibm

CVE-2021-39087

MEDIUM · 6.5 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 →
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.0.3.5, 6.1.0.0 through 6.1.0.4, and 6.1.1.0 through 6.1.1.1 could allow an authenticated user to obtain sensitive information due to improper permission controls. IBM X-Force ID: 216109.

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-6.0.3.5, 6.1.0.0-6.1.0.4, and 6.1.1.0-6.1.1.1 contains an information disclosure vulnerability where an authenticated user can obtain sensitive information due to improper permission controls, allowing unauthorized access to data beyond the user's intended authorization level.

MitigationApply the IBM security patch for this vulnerability and review user permission configurations to ensure proper access controls are enforced. Upgrade to a patched version as specified in IBM's security bulletin.

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
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 installation
    Locate the IBM Sterling B2B Integrator installation directory and confirm the product is present on the system.
    Affected if The product is installed and the version falls within the affected ranges: 6.0.0.0-6.0.3.5, 6.1.0.0-6.1.0.4, or 6.1.1.0-6.1.1.1.
  2. Determine installed version
    Check the product version information, typically found in the installation directory or via the product's about/version utility.
    Affected if The installed version is less than 6.0.3.6, 6.1.0.5, or 6.1.1.2.
  3. Verify user authentication is enabled
    Confirm that user authentication is enabled on the system, since this vulnerability requires an authenticated user to exploit.
    Affected if Authentication is enabled and users can log in to the system.
  4. Review permission configuration settings
    Inspect the user permission configurations and access control settings within the IBM Sterling B2B Integrator admin console or configuration files.
    Affected if Users may have broader data access permissions than intended, allowing unauthorized access to data beyond their assigned authorization level.

The environment is affected if IBM Sterling B2B Integrator is installed with a version in the 6.0.0.0-6.0.3.5, 6.1.0.0-6.1.0.4, or 6.1.1.0-6.1.1.1 range and user authentication is enabled, potentially allowing authenticated users to access data beyond their intended permissions.

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 security patch for this vulnerability and review user permission configurations to ensure proper access controls are enforced. Upgrade to a patched version as specified in IBM's security bulletin.

Recommended fix High confidence

6.0.3.6 / 6.1.0.5 / 6.1.1.2 (depending on current branch)

  1. Identify the currently installed IBM Sterling B2B Integrator version by checking the installation directory or system information
  2. If running 6.0.0.0 through 6.0.3.5, upgrade to version 6.0.3.6 or later
  3. If running 6.1.0.0 through 6.1.0.4, upgrade to version 6.1.0.5 or later
  4. If running 6.1.1.0 through 6.1.1.1, upgrade to version 6.1.1.2 or later
  5. After upgrade, verify the fix by testing that proper permission controls are enforced and authenticated users can no longer access sensitive information outside their authorized scope

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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