I2 Intelligent Analysis PlatformApplication · Ibm

CVE-2019-4062

HIGH · 7.1 CVSS v3.1 Published 2019-07-30
Fix available
A fix is available. Upgrade to after 9.1.1 or later.
See remediation →
77/100
Remediation priority · High
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 i2 Intelligent Analyis Platform 9.0.0 through 9.1.1 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: 157007.

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 i2 Intelligent Analysis Platform versions 9.0.0 through 9.1.1 is vulnerable to XML External Entity Injection (XXE). The application fails to properly disable external entity processing when parsing XML data, allowing a remote attacker to exploit this by crafting malicious XML that references external entities to read sensitive files from the server or cause memory exhaustion through recursive entity expansion.

MitigationDisable XML external entity (XXE) processing in the application's XML parser configuration and implement strict input validation for all XML data. Upgrade to a patched version if available from IBM.

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
I2 Intelligent Analysis PlatformApplication
Affected:>= 9.0.0, <= 9.1.1

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
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify IBM i2 Intelligent Analysis Platform is installed
    Check for the product in common installation directories such as C:\Program Files\IBM\i2\ or /opt/IBM/i2/ on Linux. On Windows, also check the list of installed programs or running services for 'IBM i2' entries.
    Affected if The product is found on the system
  2. Determine the installed version number
    Locate version information in the installation directory, typically in an About dialog within the application, a version.txt file, or product-specific metadata files in the installation folder.
    Affected if The version is 9.0.0, 9.1.0, or 9.1.1 (falls within 9.0.0 through 9.1.1 inclusive)
  3. Identify XML input vectors
    Examine the application's interfaces for any features that accept XML data: file import functionality, data ingestion endpoints, API interfaces, or any configuration import features.
    Affected if The application processes or imports XML files or data from external sources
  4. Check XML parser security configuration
    If accessible, examine the application's configuration files or XML processor settings for properties controlling external entity resolution. Look for settings related to 'external entities', 'DTD processing', or 'entity expansion' in parser configuration files.
    Affected if External entity processing is not explicitly disabled or set to secure (the application is vulnerable by default in affected versions)

The environment is affected if IBM i2 Intelligent Analysis Platform version 9.0.0 through 9.1.1 is installed and the application processes XML input, since the XXE vulnerability exists in how the application handles XML parsing in those versions.

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.

From vendor data
Upgrade available Upgrade to a release after 9.1.1
Interim mitigation

Disable XML external entity (XXE) processing in the application's XML parser configuration and implement strict input validation for all XML data. Upgrade to a patched version if available from IBM.

Fix this in I2 Intelligent Analysis Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-4062 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-4062 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