CyberSecBulletin
CVE-2022-23724NVD status: Modified

PingID Integration for Windows Login: Use of Hard-coded Credentials

Published Updated By the CyberSecBulletin desk

CVE-2022-23724 is a high-severity use of hard-coded credentials vulnerability in PingID Integration for Windows Login from Ping Identity, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected PingID Integration for Windows Login versions: 2.4.1 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.45% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of PingID Integration for Windows Login you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on docs.pingidentity.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Ping IdentityPingID Integration for Windows Login2.4.1 and earlierNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.16.4MediumCNA (pingidentity.com)
CVSS 3.18.1HighNVD
CVSS 2.05.5MediumNVD

Official description

Use of static encryption key material allows forging an authentication token to other users within a tenant organization. MFA may be bypassed by redirecting an authentication flow to a target user. To exploit the vulnerability, must have compromised user credentials.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of Hard-coded Credentials

The product contains hard-coded credentials, such as a password or cryptographic key.

How developers prevent this class of flaw

  • For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible. In Windows environments, the Encrypted File System (EFS) may provide some protection.
  • For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a first login mode that requires the user to enter a unique strong password or key.
  • If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.

More Use of Hard-coded Credentials vulnerabilities (CWE-798)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Use of Hard-coded Credentials vulnerabilities

Spotted an error? Tell us.