CVE-2022-35638
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 · uneditedIBM Sterling B2B Integrator Standard Edition 6.0.0.0 through 6.0.3.8 and 6.1.0.0 through 6.1.2.1 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 230824.
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 confidenceIBM Sterling B2B Integrator versions 6.0.0.0-6.0.3.8 and 6.1.0.0-6.1.2.1 contain a Cross-Site Request Forgery (CSRF) vulnerability that allows authenticated users to be tricked into unknowingly executing unauthorized actions via malicious requests.
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>= 6.0.0.0, < 6.0.3.9>= 6.1.0.0, < 6.1.2.3CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Sterling B2B Integrator versionAccess the IBM Sterling B2B Integrator admin console or dashboard and locate the product version information, typically found in the About or System Information section. Alternatively, check installation directory version files or release notes included with the product.Affected if The installed version is 6.0.0.0 through 6.0.3.8, or 6.1.0.0 through 6.1.2.1 (versions below 6.0.3.9 or 6.1.2.2)
A user is affected if their IBM Sterling B2B Integrator version is 6.0.0.0-6.0.3.8 or 6.1.0.0-6.1.2.1 and the web interface is exposed.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.0.3.96.1.2.3
Apply IBM's vendor patches (6.0.3.9 and 6.1.2.2) to implement anti-CSRF token protections on all state-changing endpoints.
IBM Sterling B2B Integrator 6.0.3.9 or later (6.0.x branch); IBM Sterling B2B Integrator 6.1.2.3 or later (6.1.x branch)
- 1. Schedule a maintenance window for the upgrade process
- 2. Back up the current IBM Sterling B2B Integrator installation, including configuration files and database
- 3. Download the fixed version (6.0.3.9 or later for 6.0.x branch, or 6.1.2.3 or later for 6.1.x branch) from IBM Fix Central or authorized IBM distribution channels
- 4. Stop all IBM Sterling B2B Integrator services before applying the upgrade
- 5. Apply the upgrade following IBM's standard upgrade procedures for your specific version
- 6. Verify the upgrade was successful by checking the version number in the system information
- 7. Restart all IBM Sterling B2B Integrator services
- 8. Test critical business workflows to ensure the integration functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35638 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-35638 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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