{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22700 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22700 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22700 is a medium-severity vulnerability in CyberArk Identity, published on 3 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-22700 and fix it if it is affected.\n\nWhat it is: CVE-2022-22700 is a medium-severity vulnerability in CyberArk Identity, published on 3 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-22700 in the wild and no public exploit code.\n\nAffected product: CyberArk Identity. 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-22700/ (Markdown: https://insights.sbomify.com/CVE-2022-22700/index.md)","id":"CVE-2022-22700","markdown":"https://insights.sbomify.com/CVE-2022-22700/index.md","name":"CVE-2022-22700","record":{"aliases":["GHSA-8pv4-j9f8-22xr"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Identity Management Service","requires_auth":"none","summary":"Attackers can determine if users exist in a tenant by analyzing predictable response headers in CyberArk Identity under certain configurations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Fluid Attacks","cpe":[{"product":"identity","vendor":"cyberark"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"CyberArk Identity versions up to and including 22.1 in the 'StartAuthentication' resource, exposes the response header 'X-CFY-TX-TM'. In certain configurations, that response header contains different, predictable value ranges which can be used to determine whether a user exists in the tenant.","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":"Information disclosure in CyberArk Identity","id":"CVE-2022-22700","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in PartKeepr","id":"CVE-2022-22701"},"packages":[],"prev":{"headline":"Umbraco Password Reset URL Poison","id":"CVE-2022-22691"},"products":["CyberArk Identity"],"published":"2022-03-03","related":[{"cvss_score":8.3,"headline":"CyberArk - CWE-602: Client-Side Enforcement of Server-Side Security","id":"CVE-2024-42340","kev_date_added":null,"published":"2024-08-25"},{"cvss_score":5.3,"headline":"Information disclosure in Identity","id":"CVE-2021-37151","kev_date_added":null,"published":"2021-09-01"},{"cvss_score":4.3,"headline":"CyberArk - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor","id":"CVE-2024-42337","kev_date_added":null,"published":"2024-08-25"},{"cvss_score":4.3,"headline":"CyberArk - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor","id":"CVE-2024-42338","kev_date_added":null,"published":"2024-08-25"},{"cvss_score":4.3,"headline":"CyberArk - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor","id":"CVE-2024-42339","kev_date_added":null,"published":"2024-08-25"}],"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":["n/a"]},"summary":"Attackers can determine if users exist in a tenant by analyzing predictable response headers in CyberArk Identity under certain configurations.","url":"https://insights.sbomify.com/CVE-2022-22700/"}