{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23721 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-23721 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23721 is a low-severity authentication bypass vulnerability in Ping Identity unspecified, published on 25 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23721 and fix it if it is affected.\n\nWhat it is: CVE-2022-23721 is a low-severity authentication bypass vulnerability in Ping Identity unspecified, published on 25 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-23721 in the wild and no public exploit code.\n\nAffected product: Ping Identity unspecified. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-23721/ (Markdown: https://insights.sbomify.com/CVE-2022-23721/index.md)","id":"CVE-2022-23721","markdown":"https://insights.sbomify.com/CVE-2022-23721/index.md","name":"CVE-2022-23721","record":{"aliases":["GHSA-5q72-4whc-c2w5"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows login integration","requires_auth":"low_privilege","summary":"Attackers can exploit duplicate username collisions in PingID Windows login to potentially take over accounts when users are provisioned at different times.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Ping Identity","cpe":[{"product":"pingid_integration_for_windows_login","vendor":"pingidentity"}],"cvss":{"score":3.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-694","name":"Use of Multiple Resources with Duplicate Identifier"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"PingID integration for Windows login duplicate username collision.","id":"CVE-2022-23721","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"PingFederate Password Reset via Authentication API Mishandling","id":"CVE-2022-23722"},"packages":[],"prev":{"headline":"Hardcoded credentials in PingID Windows Login","id":"CVE-2022-23720"},"products":["unspecified"],"published":"2023-04-25","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-25826","kev_date_added":null,"published":"2020-09-23"},{"cvss_score":7.7,"headline":"Information disclosure in PingID Windows Login","id":"CVE-2022-23725","kev_date_added":null,"published":"2022-06-30"},{"cvss_score":7.7,"headline":"PingID Windows Login RSA cryptographic weakness with possible offline MFA bypass","id":"CVE-2021-41992","kev_date_added":null,"published":"2022-04-30"},{"cvss_score":7.6,"headline":"PingID Windows Login prior to 2.8 uses known vulnerable components that can lead to remote code execution","id":"CVE-2022-23718","kev_date_added":null,"published":"2022-06-30"},{"cvss_score":7.5,"headline":"Hardcoded credentials in PingID Windows Login","id":"CVE-2022-23720","kev_date_added":null,"published":"2022-06-30"},{"cvss_score":7.2,"headline":"Missing authorization in PingID Windows Login","id":"CVE-2022-23719","kev_date_added":null,"published":"2022-06-30"},{"cvss_score":6.4,"headline":"PingID Integration for Windows Login MFA Bypass","id":"CVE-2022-23724","kev_date_added":null,"published":"2022-05-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-04","vendors":["Ping Identity"]},"summary":"Attackers can exploit duplicate username collisions in PingID Windows login to potentially take over accounts when users are provisioned at different times.","url":"https://insights.sbomify.com/CVE-2022-23721/"}