CVE-2022-23718
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 uses known vulnerable components that can lead to remote code execution. An attacker capable of achieving a sophisticated man-in-the-middle position, or to compromise Ping Identity web servers, could deliver malicious code that would be executed as SYSTEM by the PingID Windows Login application.
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 contain known vulnerable third-party components that can be exploited to achieve remote code execution. An attacker with a sophisticated man-in-the-middle position or who has compromised Ping Identity web servers can inject malicious code that executes with SYSTEM-level privileges on Windows systems where PingID is installed.
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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 installedOpen Windows Settings > Apps & Features, or use PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*PingID*'}Affected if PingID Windows Login does not appear in installed programs or registry
-
Retrieve the installed version numberIn Control Panel > Programs and Features, locate 'PingID Integration for Windows Login' and note the version in the Version column, or run: (Get-ItemProperty 'C:\Program Files\Ping Identity\PingID\PingIDWindowsLogin.exe').VersionInfo.FileVersion if the executable existsAffected if Version cannot be determined or is not visible
-
Compare installed version to 2.8If a version is found, compare it numerically to version 2.8. For example, versions 2.7, 2.6.1, 2.6, 2.5 are all prior to 2.8Affected if Installed version is less than 2.8 (for example, 2.7.x, 2.6.x, or any version starting with 2 followed by a number less than 8)
-
Verify the vulnerable component is presentThis CVE concerns third-party components bundled with PingID. If PingID Windows Login version is confirmed below 2.8, the vulnerable components are present by definition. No additional file inspection is required for detection purposesAffected if Version check confirms the install is below 2.8
If PingID Windows Login is installed and the version is below 2.8, the environment is affected by this CVE.
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 replace the vulnerable components. Prior to deployment, verify the upgrade does not conflict with existing identity infrastructure and test authentication flows thoroughly.
2.8
- Upgrade PingID Windows Login to version 2.8 or later
- Verify the upgrade by checking the PingID Windows Login application version
- Ensure the upgrade is performed with appropriate change management procedures
- Test that the PingID Windows Login functionality continues to work correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23718 — 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-23718 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