IBM Security Guardium Database Activity Monitor appliance could allow a local user to inject commands that would be executed as root.

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• ibm security guardium10.0
• ibm security guardium10.0.1
• ibm security guardium10.1
• ibm security guardium10.1.2
• ibm security guardium8.2
• ibm security guardium9.0
• ibm security guardium9.1
• ibm security guardium9.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.

• IBM Corporation Guardium

  • 2.5, 8.2, 9.0, 9.1, 10.0, 10, 9.5, 10.0.1, 10.1, 10.1.2affected

Other highest-scoring records for the same primary product.

• CVE-2017-1253IBM Security Guardium 10.0 could allow a remote authenticated attacker to execute arbitrary commands on the system.
  40Plan
• CVE-2017-1269IBM Security Guardium 10.0 and 10.1 is vulnerable to SQL injection.
  40Plan
• CVE-2020-4690IBM Security Guardium 11.3 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authe
  39Monitor
• CVE-2021-20418IBM Security Guardium 11.2 does not require that users should have strong passwords by default, which makes it easier for attackers to compr
  39Monitor
• CVE-2021-20426IBM Security Guardium 11.2 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authe
  39Monitor
• CVE-2020-4193IBM Security Guardium 11.1 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials.
  39Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const host = req.body.host;2exec("ping -c 1 " + host, onResult);

1const host = req.body.host;2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);3execFile("ping", ["-c", "1", host], onResult);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.