CVE-2019-4513
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 Security Access Manager for Enterprise Single Sign-On 8.2.2 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 164555.
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 Security Access Manager for Enterprise Single Sign-On 8.2.2 is vulnerable to XML External Entity Injection (XXE) when processing XML data. A remote attacker can exploit this by injecting malicious external entity references to expose sensitive information from the system or cause memory exhaustion through recursive entity expansion.
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= 8.2.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.1/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.
-
Confirm IBM ISAM ESSO installationLocate the IBM Security Access Manager for Enterprise Single Sign-On installation directory or check installed programs on the system. Look for directories or registry entries containing 'ISAM' or 'IBM Security Access Manager' and 'SSO'.Affected if The product is installed on the system and is version 8.2.2
-
Verify exact version numberCheck the product version through the administrative console, installation logs, or by querying the installed software version. Compare the installed version against the affected range: version 8.2.2 exactly.Affected if The installed version is exactly 8.2.2
-
Identify XML processing functionalityLocate XML import, parsing, or configuration features within the ISAM ESSO administration interface or file system. Look for functions that accept XML input such as configuration imports, user imports, or policy imports.Affected if The product has XML processing capabilities that handle incoming XML data
-
Check XML parser configurationInspect the XML parser configuration files or settings within the ISAM ESSO installation to determine if external entity processing and DTD processing are enabled. Look for XML parser settings in configuration directories.Affected if External entity processing and DTD processing are enabled in the XML parser configuration
A system is affected if IBM Security Access Manager for Enterprise Single Sign-On version 8.2.2 is installed and the XML parser has external entity and DTD processing enabled for features that process untrusted XML input.
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 and DTDs in XML parsers, implement input validation for XML data, and apply the vendor patch when available from IBM.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4513 — 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-2019-4513 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