CVE-2020-4430 — IBM Data Risk Manager Directory Traversal Vulnerability
IBM Data Risk Manager 2.0.1, 2.0.2, 2.0.3, and 2.0.4 could allow a remote authenticated attacker to traverse directories on the system. An attacker could send a specially-crafted URL request to download arbitrary files from the system. IBM X-Force ID: 180535.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- EPSS 68.5% (30-day exploitation probability)+15
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — www.ibm.com (NIST National Vulnerability Database)
CISA required action CISA
Apply updates per vendor instructions.
US federal deadline: May 3, 2022 — passed 1626 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Ibm Data Risk Manager).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Ibm | Data Risk Manager | ≥ 2.0.1 and ≤ 2.0.4 | Vulnerable | NIST National Vulnerability Database |
| Ibm | Data Risk Manager | version 2.0.1version 2.0.2version 2.0.3version 2.0.4version 2.0.5version 2.0.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 4.3 | CVSS 3.1 | Medium | 2.8 | 1.4 | nvd@nist.gov via NIST National Vulnerability Database |
| 4.3 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 4.3 | CVSS 3.0 | Medium | 2.8 | 1.4 | psirt@us.ibm.com via NIST National Vulnerability Database |
| 4.3 | CVSS 3.0 | Medium | — | — | ibm via CVE Program (cve.org) e CISA ADP |
| 4.0 | CVSS 2.0 | Medium | 8.0 | 2.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 68.54%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor file creation in web directories and paths with traversal sequences (../).
- Hunt retroactively in logs from before Nov 3, 2021 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · ibm/data risk manager
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · ibm/data risk manager
- CVSS changed · 4.3
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2021
- Added to CISA KEV catalog
- 2020
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
7 on the record
- exchange.xforce.ibmcloud.com/vulnerabilities/180535
- www.ibm.com/support/pages/node/6206875
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- seclists.org/fulldisclosure/2024/Nov/0
- github.com/advisories/GHSA-86cc-wh6w-cw2h
- seclists.org/fulldisclosure/2024/Nov/1
- nvd.nist.gov/vuln/detail/CVE-2020-4430
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2020-4427 IBM Data Risk Manager Security Bypass Vulnerability KEV May 7, 2020
- Critical CVE-2020-4428 IBM Data Risk Manager Remote Code Execution Vulnerability KEV May 7, 2020
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2020-4430 is "IBM Data Risk Manager Directory Traversal Vulnerability", rated Medium. It affects Data Risk Manager (Ibm); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 4.3 describes technical severity. EPSS 68.54% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.