CVE-2020-4761
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 5.2.0.0 through 5.2.6.5_2, 6.0.0.0 through 6.0.3.2, and 6.1.0.0 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system. IBM X-Force ID: 188895.
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 confidenceIBM Sterling B2B Integrator returns detailed technical error messages directly in browser responses, exposing internal system information such as stack traces, file paths, configuration details, or database structures. This information disclosure could aid attackers in reconnaissance and planning further attacks against the system.
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>= 5.2.0.0, <= 5.2.6.5_2>= 6.0.0.0, <= 6.0.3.2= 6.1.0.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Sterling B2B Integrator versionLocate the version file in the installation directory (typically named version.txt, about.txt, or in installer properties under the installation root). Run: find /IBM -name "version*" -o -name "*about*" 2>/dev/null or check the installer_properties file.Affected if The installed version falls within 5.2.0.0 to 5.2.6.5_2, 6.0.0.0 to 6.0.3.2, or is exactly 6.1.0.0
-
Verify web.xml custom error page configurationLocate the web.xml configuration file in the application server (typically in <install_dir>/etc/ or <install_dir>/properties/). Open web.xml and search for <error-page> elements.Affected if No <error-page> elements are defined, or the error-page configuration points to generic templates rather than custom error handling pages, meaning verbose stack traces may be returned.
-
Check for verbose error messaging in application serverInspect the application server configuration files for settings that control error verbosity. Look for parameters like showStackTrace, includeStackTrace, or verboseError in IBM-specific configuration files.Affected if Verbose error settings are enabled (value set to true or similar), indicating detailed error information may be exposed.
-
Test for error information disclosure via HTTPTrigger an intentional error condition by making a request to the application with malformed input or accessing a non-existent resource. Inspect the HTTP response headers and body for stack traces, file paths, or database structure details.Affected if The response contains stack traces, absolute file paths, configuration details, or database schema information.
You are affected if your installed version is within the affected ranges AND verbose error messages are returned in HTTP responses without custom error page handling.
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.
From vendor dataConfigure custom error pages and disable verbose error messaging in the application server (typically via web.xml or IBM-specific configuration). Apply IBM patches if available for versions 5.2.6.5_2, 6.0.3.2, and 6.1.0.0.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-4761 — 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-2020-4761 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