# CVE-2020-4427: IBM Data Risk Manager Security Bypass

> Remote attackers can bypass authentication via crafted HTTP requests in SAML configurations to gain full administrative access.

- **Severity:** Critical 9.0 (`CVSS:3.0/I:H/UI:N/PR:N/C:H/A:H/AV:N/S:C/AC:H/RL:O/RC:C/E:U`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2020
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-24c2-gvwg-5p45

## What is CVE-2020-4427?

CVE-2020-4427 is a critical authentication bypass vulnerability in IBM Data Risk Manager, published on 7 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2020-4427?

It affects 1 product.


Products: Ibm Data Risk Manager.

## How do I fix CVE-2020-4427?

No fix has been published for CVE-2020-4427 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-4427 being exploited?

Yes. Attackers have exploited CVE-2020-4427 in the wild since at least 3 Nov 2021.

Public exploit code:

- IBM Data Risk Manager Arbitrary File Download (metasploit)
- IBM Data Risk Manager Unauthenticated Remote Code Execution (metasploit)
- IBM Data Risk Manager - Authentication Bypass via SAML (nuclei): http/cves/2020/CVE-2020-4427.yaml

## Other vulnerabilities in IBM Data Risk Manager

- [CVE-2020-4428](https://insights.sbomify.com/CVE-2020-4428/): IBM Data Risk Manager Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2020-4430](https://insights.sbomify.com/CVE-2020-4430/): IBM Data Risk Manager Directory Traversal (medium 4.3, exploited in the wild)
- [CVE-2020-4429](https://insights.sbomify.com/CVE-2020-4429/): Hardcoded credentials in Data Risk Manager (critical 10.0)
- [CVE-2020-4611](https://insights.sbomify.com/CVE-2020-4611/): Privilege escalation in Data Risk Manager (high 8.8)
- [CVE-2020-4620](https://insights.sbomify.com/CVE-2020-4620/): File upload in Data Risk Manager (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-4427 and fix it if it is affected.

What it is: CVE-2020-4427 is a critical authentication bypass vulnerability in IBM Data Risk Manager, published on 7 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-4427 in the wild since at least 3 Nov 2021.

Affected product: IBM Data Risk Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-4427/ (Markdown: https://insights.sbomify.com/CVE-2020-4427/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-4427
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-4427
- OSV: https://osv.dev/vulnerability/CVE-2020-4427

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-4427/
Summaries are generated and may contain mistakes; the official description above is the record.