CVE-2017-1192
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 5.2 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose highly sensitive information or consume memory resources. IBM X-Force ID: 123663.
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 5.2 is vulnerable to XML External Entity Injection (XXE) when processing XML data. A remote attacker can exploit this to read sensitive files from the server filesystem or cause denial-of-service through memory resource consumption.
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.2CVSS 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
- High
- Integrity
- None
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
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.
-
Locate IBM Sterling B2B Integrator installation and versionCheck the installation directory for version files, or run the product version command (typically found in the installation bin directory, such as 'version.sh' or through the admin console)Affected if The installed version is exactly 5.2 (matching the affected version range)
-
Identify if XML processing is enabledReview the product configuration files (typically in the 'config' or 'properties' directory under the installation root) for XML input processing settings, or check the admin console for XML handler configurationsAffected if XML input processing or XML handler features are configured and active in the system
-
Examine XML parser configuration for external entity settingsLocate the XML parser configuration files (commonly 'parser.xml', 'xml-config.xml', or similar in the config directory) and inspect settings related to 'external-entities', 'entity-resolver', or 'xxe' processingAffected if The XML parser configuration allows external entity resolution (e.g., feature flags for external entities are not disabled, or no XXE protection is configured)
-
Check deployed adapters or connectors using XML inputReview deployed integration adapters, trading partner configurations, or map scripts that process XML messages, particularly those handling B2B document types (EDI, XML, etc.)Affected if There are active adapters or configurations that process untrusted XML input from external trading partners
You are affected if IBM Sterling B2B Integrator version 5.2 is installed AND XML processing is enabled with external entity parsing allowed in the configuration.
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 dataDisable external entity processing in the XML parser configuration and apply the IBM patch for CVE-2017-1192. Validate and sanitize all XML input before processing.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1192 — 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-2017-1192 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