PingID Windows Login prior to 2.8 does not properly set permissions on the Windows Registry entries used to store sensitive API keys under some circumstances

published 2022-06-30 4y ago modified 2026-06-17 4mo ago also EUVD-2022-28661

cvss: 7.7; 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 Windows Login prior to 2.8 does not properly set permissions on the Windows Registry entries used to store sensitive API keys under some circumstances.

Patch / fix

fixed in 1

Ping Identity PingID Windows Login 2.8

Is CVE-2022-23725 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.7	CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

Ping Identity PingID Windows Login

Classification

Weakness

CWE-522 Insufficiently Protected Credentials
CWE-288 Authentication Bypass Using an Alternate Path or Channel
CWE-732 Incorrect Permission Assignment for Critical Resource

References

pingidentity.com /en/resources/downloads/pingid.html
vendor-advisory
docs.pingidentity.com /bundle/pingid/page/zhy1653552428545.html
vendor-advisory

Sources

CVE List CVE-2022-23725
NVD CVE-2022-23725

Fencer Intel 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.