{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-37151 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-37151 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-37151 is a medium-severity vulnerability in CyberArk Identity, published on 1 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-37151 and fix it if it is affected.\n\nWhat it is: CVE-2021-37151 is a medium-severity vulnerability in CyberArk Identity, published on 1 Sep 2021. 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-2021-37151 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-2021-37151/ (Markdown: https://insights.sbomify.com/CVE-2021-37151/index.md)","id":"CVE-2021-37151","markdown":"https://insights.sbomify.com/CVE-2021-37151/index.md","name":"CVE-2021-37151","record":{"aliases":["GHSA-rq35-f9g6-4534"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Identity management","requires_auth":"none","summary":"Attackers can enumerate valid usernames via response length differences in specific MFA configurations, aiding brute-force attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCD","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-203","name":"Observable Discrepancy"}],"description":"CyberArk Identity 21.5.131, when handling an invalid authentication attempt, sometimes reveals whether the username is valid. In certain authentication policy configurations with MFA, the API response length can be used to differentiate between a valid user and an invalid one (aka Username Enumeration). Response differentiation enables attackers to enumerate usernames of valid application users. Attackers can use this information to leverage brute-force and dictionary attacks in order to discover valid account information such as passwords.","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 Identity","id":"CVE-2021-37151","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-37152"},"packages":[],"prev":{"headline":"Protocol vs scheme mismatch","id":"CVE-2021-37150"},"products":["Identity"],"published":"2021-09-01","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 CyberArk Identity","id":"CVE-2022-22700","kev_date_added":null,"published":"2022-03-03"},{"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-04","vendors":["CyberArk"]},"summary":"Attackers can enumerate valid usernames via response length differences in specific MFA configurations, aiding brute-force attacks.","url":"https://insights.sbomify.com/CVE-2021-37151/"}