IBM Security Identity Governance and Intelligence 5.2 through 5.2.4.1 Virtual Appliance contains hard-coded credentials, such as a password

Affected versions

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

• ibm security identity governance and intelligence5.2 and later · up to 5.2.4.1 inclusive

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 Security Identity Governance and Intelligence

  • 5.2, 5.2.1, 5.2.2, 5.2.2.1, 5.2.3, 5.2.3.1, 5.2.3.2, 5.2.4, 5.2.4.1affected

Other highest-scoring records for the same primary product.

• CVE-2020-4958IBM Security Identity Governance and Intelligence 5.2.6 does not perform any authentication for functionality that requires a provable user
  40Plan
• CVE-2017-1407IBM Security Identity Manager Virtual Appliance 6.0 and 7.0 could allow a remote authenticated attacker to execute arbitrary commands on the
  36Monitor
• CVE-2017-1483IBM Security Identity Manager Adapters 6.0 and 7.0 does not perform an authentication check for a critical resource or functionality allowin
  34Monitor
• CVE-2020-4795IBM Security Identity Governance and Intelligence 5.2.6 could disclose sensitive information to an unauthorized user using a specially craft
  33Monitor
• CVE-2018-1756IBM Security Identity Governance and Intelligence 5.2.3.2 and 5.2.4 is vulnerable to SQL injection.
  33Monitor
• CVE-2017-1396IBM Security Identity Governance Virtual Appliance 5.2 through 5.2.3.2 specifies permissions for a security-critical resource in a way that
  32Monitor

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

Root cause

For convenience in support or manufacturing, an account that is identical on every device is embedded in the software. Credentials learned from one device work on all of them.

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

1const SUPPORT_USER = "support";2const SUPPORT_PASS = "hardcoded-password";

1const creds = await provisioning.deviceCredentials(deviceId);2if (creds.mustRotate) await forcePasswordChange(deviceId);

Attack context

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