Skip to content

Product

ibm data risk manager vulnerabilities

18 published CVES affecting ibm data risk manager, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
18
Critical
3
High
8
Medium
7
Low
0
Unscored
0
CISA KEV
3

Latest ibm data risk manager CVEs

Newest publication first

  1. HighCVSS 7.5 EPSS 1.2%

    IBM Data Risk Manager (iDNA) 2.0.6 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID: 184983.

  2. HighCVSS 8.8 EPSS 5.2%

    IBM Data Risk Manager (iDNA) 2.0.6 could allow a remote authenticated attacker to upload arbitrary files, caused by the improper validation of file extensions. By sending a specially-crafted HTTP request, a remote attacker could exploit this vulnerability to upload a malicious fi...

  3. MediumCVSS 5.4 EPSS 0.67%

    IBM Data Risk Manager (iDNA) 2.0.6 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force...

  4. MediumCVSS 4.3 EPSS 68.5% CISA KEV added 2021-11-03 Exploited in the wild

    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.

  5. CriticalCVSS 9.8 EPSS 72.0% Framework module

    IBM Data Risk Manager 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, and 2.0.6 contains a default password for an IDRM administrative account. A remote attacker could exploit this vulnerability to login and execute arbitrary code on the system with root privileges. IBM X-Force ID: 180534.

  6. CriticalCVSS 9.8 EPSS 70.0% CISA KEV added 2021-11-03 Exploited in the wild Framework module

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

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.