PingID integration for Windows login duplicate username collision.

published 2023-04-25 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-28657

cvss: 3.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits: 0; none known

PingID integration for Windows login prior to 2.9 does not handle duplicate usernames, which can lead to a username collision when two people with the same username are provisioned onto the same machine at different times.

Patch / fix

fixed in 1

pingidentity pingid_integration_for_windows_login 2.9

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 21 mo ago (2025-02-04)

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	3.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L
NVD	3.1	3.3	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Classification

Weakness

CWE-694 Use of Multiple Resources with Duplicate Identifier
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

docs.pingidentity.com /r/en-us/pingid/davinci_pingid_windows_login_relnotes_2.9
release-notes

Sources

CVE List CVE-2022-23721
NVD CVE-2022-23721

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary