IBM Guardium Data Encryption vulnerabilities
29 CVEs affecting IBM Guardium Data Encryption, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2021-39024, published 2022-05-10.
More from IBM.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2019-4713, published 2020-08-26. High severity, CVSS 8.8. EPSS: 2.6% chance of exploitation in the next 30 days. IBM Security Guardium Data Encryption (GDE) 3.0.0.2 could allow a remote authenticated attacker to execute arbitrary commands on the system. By sending a specially-crafted request, an attacker could…
- CVE-2019-4694, published 2020-08-26. Critical severity, CVSS 9.8. EPSS: 1.2% chance of exploitation in the next 30 days. IBM Security Guardium Data Encryption (GDE) 3.0.0.2 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication…
- CVE-2021-20415, published 2021-07-07. High severity, CVSS 7.5. EPSS: 0.9% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 4.0.0.4 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials. IBM X-Force ID: 196217.
- CVE-2021-39023, published 2022-05-06. High severity, CVSS 7.5. EPSS: 0.9% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 4.0.0 and 5.0.0 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information…
- CVE-2019-4698, published 2020-08-26. High severity, CVSS 7.5. EPSS: 0.8% chance of exploitation in the next 30 days. IBM Security Guardium Data Encryption (GDE) 3.0.0.2 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force…
- CVE-2021-20413, published 2021-06-28. Medium severity, CVSS 4.3. EPSS: 0.8% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 4.0.0.4 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be…
- CVE-2021-20416, published 2021-07-07. Medium severity, CVSS 5.3. EPSS: 0.7% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 3.0.0.3 and 4.0.0.4 could allow a remote attacker to obtain sensitive information, caused by the failure to set the HTTPOnly flag. A remote attacker could exploit…
- CVE-2019-4701, published 2020-08-26. Medium severity, CVSS 5.3. EPSS: 0.7% chance of exploitation in the next 30 days. IBM Security Guardium Data Encryption (GDE) 3.0.0.2 is deployed with active debugging code that can create unintended entry points. IBM X-Force ID: 171936.
- CVE-2019-4692, published 2020-08-26. Medium severity, CVSS 5.3. EPSS: 0.7% chance of exploitation in the next 30 days. IBM Security Guardium Data Encryption (GDE) 3.0.0.2 discloses sensitive information to unauthorized users. The information can be used to mount further attacks on the system. IBM X-Force ID: 171829.
- CVE-2021-20417, published 2021-07-07. Medium severity, CVSS 4.3. EPSS: 0.6% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 4.0.0.4 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be…
Latest
- CVE-2021-39024, published 2022-05-10. Medium severity, CVSS 6.1. EPSS: 0.4% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 4.0.0.0 and 5.0.0.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the…
- CVE-2021-39027, published 2022-05-06. Medium severity, CVSS 5.0. EPSS: 0.3% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 4.0.0 and 5.0.0 prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly.…
- CVE-2021-39020, published 2022-05-05. Medium severity, CVSS 5.3. EPSS: 0.5% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 4.0.0.7 and lower stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server…
- CVE-2021-39025, published 2022-03-10. Medium severity, CVSS 5.3. EPSS: 0.6% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 4.0.0.0 and 5.0.0.0 could disclose internal IP address information when the web backend is down. IBM X-Force 213863.
- CVE-2021-39022, published 2022-03-10. High severity, CVSS 8.8. EPSS: 0.5% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 4.0.0.0 and 5.0.0.0 saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements…
- CVE-2021-39026, published 2022-02-18. Medium severity, CVSS 5.9. EPSS: 0.5% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 5.0.0.2 and 5.0.0.3 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An…
- CVE-2021-39021, published 2022-02-02. Medium severity, CVSS 5.3. EPSS: 0.5% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 5.0.0.2 behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which could facilitate…
- CVE-2021-20414, published 2021-07-12. Medium severity, CVSS 4.9. EPSS: 0.5% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 3.0.0.2 could allow a user to bruce force sensitive information due to not properly limiting the number of interactions. IBM X-Force ID: 196216.
- CVE-2021-20474, published 2021-07-07. High severity, CVSS 7.5. EPSS: 0.5% chance of exploitation in the next 30 days. IBM Guardium Data Encryption (GDE) 3.0.0.2 and 4.0.0.4 does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.