{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23720 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-23720 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23720 is a high-severity vulnerability in PingID Windows Login, published on 30 Jun 2022. 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-23720 and fix it if it is affected.\n\nWhat it is: CVE-2022-23720 is a high-severity vulnerability in PingID Windows Login, published on 30 Jun 2022. 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-23720 in the wild and no public exploit code.\n\nAffected product: PingID Windows Login. 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-23720/ (Markdown: https://insights.sbomify.com/CVE-2022-23720/index.md)","id":"CVE-2022-23720","markdown":"https://insights.sbomify.com/CVE-2022-23720/index.md","name":"CVE-2022-23720","record":{"aliases":["GHSA-79g3-7482-2jvc"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"PingID Windows Login","requires_auth":"high_privilege","summary":"Misconfigured PingID Windows Login exposes full-permission API credentials, allowing attackers to perform administrative actions against PingID APIs.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Ping Identity","cpe":[{"product":"pingid_integration_for_windows_login","vendor":"pingidentity"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-648","name":"Incorrect Use of Privileged APIs"},{"id":"CWE-269","name":"Improper Privilege Management"},{"id":"CWE-288","name":"Authentication Bypass Using an Alternate Path or Channel"}],"description":"PingID Windows Login prior to 2.8 does not alert or halt operation if it has been provisioned with the full permissions PingID properties file. An IT administrator could mistakenly deploy administrator privileged PingID API credentials, such as those typically used by PingFederate, into PingID Windows Login user endpoints. Using sensitive full permissions properties file outside of a privileged trust boundary leads to an increased risk of exposure or discovery, and an attacker could leverage these credentials to perform administrative actions against PingID APIs or endpoints.","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":"Hardcoded credentials in PingID Windows Login","id":"CVE-2022-23720","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"PingID integration for Windows login duplicate username collision.","id":"CVE-2022-23721"},"packages":[],"prev":{"headline":"Missing authorization in PingID Windows Login","id":"CVE-2022-23719"},"products":["PingID Windows Login"],"published":"2022-06-30","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.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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Ping Identity"]},"summary":"Misconfigured PingID Windows Login exposes full-permission API credentials, allowing attackers to perform administrative actions against PingID APIs.","url":"https://insights.sbomify.com/CVE-2022-23720/"}