CVE-2022-23719
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPingID 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePingID Windows Login versions prior to 2.8 lack authentication on communications with a local Java service that handles security key requests. An attacker with prior code execution on the target machine can spoof this local Java service to escalate privileges to SYSTEM level execution or cause denial of service for offline security key authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if PingID Windows Login is installedSearch for PingID Windows Login in Windows Programs and Features, or look for PingID installation directories such as C:\Program Files\PingIdentity or C:\Program Files (x86)\PingIdentityAffected if If PingID Windows Login is present on the system
-
Determine the installed versionRight-click the PingID Windows Login entry in Programs and Features and select Properties, or check the version field in the installer/display nameAffected if If version information can be retrieved from the installation
-
Compare version to affected rangeCompare the installed version number to 2.8. Versions prior to 2.8 (such as 2.7.x, 2.6.x, etc.) are within the affected rangeAffected if If the installed version is less than 2.8 (for example, 2.7, 2.6, 1.x)
-
Identify the local Java serviceLook for a Java-based service or process related to PingID running locally. Check Windows Services or Task Manager for PingID-related Java processesAffected if If the PingID Java service is running and accessible locally without authentication
A system is affected if PingID Windows Login is installed with a version prior to 2.8 and the local Java service is operational.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.8
Upgrade PingID Windows Login to version 2.8 or later to implement proper authentication on the local Java service communication.
PingID Windows Login 2.8
- Verify current installed version of PingID Windows Login on affected systems
- Download PingID Windows Login version 2.8 or later from the official PingIdentity download portal
- Review upgrade documentation for PingID Windows Login 2.8
- Schedule maintenance window for the upgrade process
- Backup current PingID Windows Login configuration
- Install version 2.8 on all affected Windows machines
- Verify the upgrade was successful by checking the installed version
- Test that security key authentication functions correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23719 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data