{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-3557 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-3557 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-3557 is a medium-severity missing authorization vulnerability in Argoproj Argo Cd, published on 16 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-3557 and fix it if it is affected.\n\nWhat it is: CVE-2021-3557 is a medium-severity missing authorization vulnerability in Argoproj Argo Cd, published on 16 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-3557 in the wild and no public exploit code.\n\nAffected product: Argoproj Argo Cd. 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-3557/ (Markdown: https://insights.sbomify.com/CVE-2021-3557/index.md)","id":"CVE-2021-3557","markdown":"https://insights.sbomify.com/CVE-2021-3557/index.md","name":"CVE-2021-3557","record":{"aliases":["GHSA-8fgv-frq2-3468"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"ArgoCD GitOps tool","requires_auth":"low_privilege","summary":"Unprivileged users can deploy ArgoCD in their namespace to read all cluster resources, including secrets, enabling privilege escalation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"argo_cd","vendor":"argoproj"},{"product":"openshift_gitops","vendor":"redhat"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"A flaw was found in argocd. Any unprivileged user is able to deploy argocd in their namespace and with the created ServiceAccount argocd-argocd-server, the unprivileged user is able to read all resources of the cluster including all secrets which might enable privilege escalations. The highest threat from this vulnerability is to data confidentiality.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Missing authorization in argocd","id":"CVE-2021-3557","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"argoproj:argo_cd","products":["argoproj:argo_cd"],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2021-3558"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2021-3556"},"products":["argocd"],"published":"2022-02-16","related":[{"cvss_score":10,"headline":"Argo CD: Project API Token Exposes Repository Credentials","id":"CVE-2025-55190","kev_date_added":null,"published":"2025-09-04"},{"cvss_score":10,"headline":"Argo CD will blindly trust JWT claims if anonymous access is enabled","id":"CVE-2022-29165","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":9.9,"headline":"Cluster secret might leak in cluster details page in Argo CD","id":"CVE-2023-40029","kev_date_added":null,"published":"2023-09-07"},{"cvss_score":9.9,"headline":"Improper access control allows admin privilege escalation in Argo CD","id":"CVE-2022-24768","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":9.8,"headline":"Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss","id":"CVE-2024-21652","kev_date_added":null,"published":"2024-03-18"},{"cvss_score":9.6,"headline":"ArgoCD ServerSideDiff is vulnerable to Kubernetes Secret Extraction","id":"CVE-2026-42880","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":9.1,"headline":"Argo CD allows cross-site scripting on repositories page","id":"CVE-2025-47933","kev_date_added":null,"published":"2025-05-29"}],"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":"Unprivileged users can deploy ArgoCD in their namespace to read all cluster resources, including secrets, enabling privilege escalation.","url":"https://insights.sbomify.com/CVE-2021-3557/"}