{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5425 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-5425 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-5425 is a high-severity authentication bypass vulnerability in Single Sign-On for VMware Tanzu, published on 31 Oct 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-5425 and fix it if it is affected.\n\nWhat it is: CVE-2020-5425 is a high-severity authentication bypass vulnerability in Single Sign-On for VMware Tanzu, published on 31 Oct 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-5425 in the wild and no public exploit code.\n\nAffected product: Single Sign-On for VMware Tanzu. 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-2020-5425/ (Markdown: https://insights.sbomify.com/CVE-2020-5425/index.md)","id":"CVE-2020-5425","markdown":"https://insights.sbomify.com/CVE-2020-5425/index.md","name":"CVE-2020-5425","record":{"aliases":["GHSA-vmxh-mp6w-252x"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"VMware Tanzu SSO","requires_auth":"high_privilege","summary":"Attackers can impersonate users and gain their permissions in VMware Tanzu SSO if specific SAML configurations and duplicate usernames exist.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"pivotal","cpe":[{"product":"single_sign-on_for_tanzu","vendor":"vmware"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Single Sign-On for Vmware Tanzu all versions prior to 1.11.3 ,1.12.x versions prior to 1.12.4 and 1.13.x prior to 1.13.1 are vulnerable to user impersonation attack.If two users are logged in to the SSO operator dashboard at the same time, with the same username, from two different identity providers, one can acquire the token of the other and thus operate with their permissions. Note: Foundation may be vulnerable only if: 1) The system zone is set up to use a SAML identity provider 2) There are internal users that have the same username as users in the external SAML provider 3) Those duplicate-named users have the scope to access the SSO operator dashboard 4) The vulnerability doesn't appear with LDAP because of chained authentication.","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":"User Impersonation possible in Tanzu SSO","id":"CVE-2020-5425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Scheduler for TAS can transmit privileged UAA token in plaintext","id":"CVE-2020-5426"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2020-5424"},"products":["Single Sign-On for VMware Tanzu"],"published":"2020-10-31","related":[],"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-09-17","vendors":["VMware Tanzu"]},"summary":"Attackers can impersonate users and gain their permissions in VMware Tanzu SSO if specific SAML configurations and duplicate usernames exist.","url":"https://insights.sbomify.com/CVE-2020-5425/"}