CVE-2020-4427: IBM Data Risk Manager Security Bypass
IBM Data Risk Manager · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.0 (CVE record)
- 9.0
- critical
- EPSS (exploit probability, 30 days)
- 70%
- higher than 99.3% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2020-4427 explained
CVE-2020-4427 is an authentication bypass in IBM Data Risk Manager affecting systems configured with SAML authentication. A remote attacker could bypass the authentication process and gain full administrative access. CISA lists it as known to be exploited, so affected deployments warrant prompt attention.
Impact
An unauthenticated remote attacker can send a specially crafted HTTP request to bypass authentication and obtain full administrative access to the system. No user interaction is required, though attack complexity is rated high and the issue applies when SAML authentication is configured. Confidentiality, integrity and availability impacts are all high, with changed scope. CISA rates it automatable with total technical impact, and attackers are known to exploit it.
Who is affected
IBM Data Risk Manager versions 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5 and 2.0.6 are affected when configured with SAML authentication. The CVE record names no fixed version. Check the IBM vendor advisory for the update that addresses this issue.
Written with AI from the data on this page and checked against it automatically.
Official 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.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- IBM Data Risk ManagerAffectedFixed in
- 2.0.1
- 2.0.2
- 2.0.3
- 2.0.4
- 2.0.5
- 2.0.6
not stated
| Product | Affected | Fixed in |
|---|---|---|
| IBM Data Risk Manager |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: ibm.com/support/pages/node/6206875
- CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply IBM's updates for Data Risk Manager per the vendor advisory, as CISA's required action states.
- Identify all Data Risk Manager instances running
2.0.1through the listed versions and check whether SAML authentication is configured. - Restrict network access to Data Risk Manager so it is not reachable from the internet or untrusted networks.
- Review administrative accounts, configuration changes and access logs for signs of compromise.
The CVE record names no fixed version. Follow the IBM vendor advisory for the update and apply it as CISA requires ("Apply updates per vendor instructions."). Until updated, limit network access to the system to trusted administrators and monitor for unauthorized administrative activity.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-287 Improper Authentication
Questions about CVE-2020-4427
- Is CVE-2020-4427 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, with a US federal due date of 2022-05-03. Known ransomware use is listed as unknown.
- Are all Data Risk Manager deployments affected?
- The description says versions
2.0.1to2.0.6as listed are affected when configured with SAML authentication. - Which version fixes the issue?
- The CVE record names no fixed version. Consult the IBM vendor advisory for the update and apply it per vendor instructions.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.