CVE-2020-4463 in the critical feed json
IBM Maximo Asset Management 7.6.0.1 and 7.6.0.2 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data.
published 6y ago modified 4mo ago also EUVD-2020-25710
- cvss
- 8.2
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 31.6%
- EPSS 31.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
IBM Maximo Asset Management 7.6.0.1 and 7.6.0.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: 181484.
Patch / fix
- ibm.com/support/pages/node/6253953 advisory
Is CVE-2020-4463 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
31.59% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template IBM Maximo Asset Management Information Disclosure - XML External Entity Injection nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.2 | CVSS:3.0/S:U/PR:N/UI:N/AV:N/I:N/C:H/AC:L/A:L/RL:O/RC:C/E:U |
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L |
| CNA | 3.0 | 8.2 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:N/A:P |
Affected products
- IBM Maximo Asset Management
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
ibm.com
/support/pages/node/6253953
patch, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/181484
vdb-entry, vendor-advisory
Sources
- CVE List CVE-2020-4463
- NVD CVE-2020-4463
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.