CVE-2020-4427
CVE-2020-4427 is a critical-severity vulnerability (CVSS 3.0 base score 9.0). IBM Data Risk Manager contains a security bypass vulnerability that could allow a remote attacker to bypass security restrictions when configured with SAML authentication. CISA added it to the Known Exploited Vulnerabilities catalog on 2021-11-03, with a remediation due date of 2022-05-03 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 70.0% probability of exploitation in the next 30 days, in the 99th percentile of scored CVEs.
Updated
- CVSS 3.0
- 9.0 CRITICAL
- EPSS
- 70.0% (99th pct)
- CISA KEV
- Exploited
- Published
- 2020-05-07
- Weakness
- CWE-287
IBM Data Risk Manager Security Bypass Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply updates per vendor instructions.
CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2020-4427
Description
IBM Data Risk Manager 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, and 2.0.6 could allow a remote attacker to bypass security restrictions when configured with SAML authentication. By sending a specially crafted HTTP request, an attacker could exploit this vulnerability to bypass the authentication process and gain full administrative access to the system. IBM X-Force ID: 180532.
Key Findings
as of 2026-11-22- CISA added CVE-2020-4427 to the KEV catalog 545 days after its CVE record was published.
- It is one of 9 IBM entries in the CISA KEV catalog, and one of 4 added in 2021.
- Its current EPSS score (70.0%) is higher than that of 56% of CISA KEV entries.
Severity
CVSS:3.0/I:H/UI:N/PR:N/C:H/A:H/AV:N/S:C/AC:H/RL:O/RC:C/E:UOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable yes, technical impact total, 2025-02-07).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| IBM | IBM Data Risk Manager | 2.0.1 2.0.2 2.0.3 2.0.4 2.0.5 2.0.6 |
References
4 linksRecord Details
- Publicly disclosed
- 2020-04-21
- Published
- 2020-05-07
- Last updated
- 2025-11-03
- Assigner (CNA)
- ibm
- Credited to
- -
More from IBM
IBM Data Risk Manager Directory Traversal Vulnerability
IBM Data Risk Manager Remote Code Execution Vulnerability
IBM Aspera Faspex code execution
IBM Planning Analytics Remote Code Execution Vulnerability
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.