{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-43832 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43832 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43832 is a critical missing authorization vulnerability in spinnaker, published on 4 Jan 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-2021-43832 and fix it if it is affected.\n\nWhat it is: CVE-2021-43832 is a critical missing authorization vulnerability in spinnaker, published on 4 Jan 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-2021-43832 in the wild and no public exploit code.\n\nAffected product: spinnaker. 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-43832/ (Markdown: https://insights.sbomify.com/CVE-2021-43832/index.md)","id":"CVE-2021-43832","markdown":"https://insights.sbomify.com/CVE-2021-43832/index.md","name":"CVE-2021-43832","record":{"aliases":[],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Spinnaker CD platform","requires_auth":"none","summary":"Unauthenticated users can create and execute pipelines in Spinnaker if RBAC is not configured, allowing remote code execution and resource deployment.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"spinnaker","vendor":"linuxfoundation"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Spinnaker is an open source, multi-cloud continuous delivery platform. Spinnaker has improper permissions allowing pipeline creation \u0026 execution. This lets an arbitrary user with access to the gate endpoint to create a pipeline and execute it without authentication. If users haven't setup Role-based access control (RBAC) with-in spinnaker, this enables remote execution and access to deploy almost any resources on any account. Patches are available on the latest releases of the supported branches and users are advised to upgrade as soon as possible. Users unable to upgrade should enable RBAC on ALL accounts and applications. This mitigates the ability of a pipeline to affect any accounts. Block application access unless permission are enabled. Users should make sure ALL application creation is restricted via appropriate wildcards.","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":"Improper Access Control in spinnaker","id":"CVE-2021-43832","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Account takeover in eLabFTW","id":"CVE-2021-43833"},"packages":[],"prev":{"headline":"Files on the host computer can be accessed from the Gradio interface","id":"CVE-2021-43831"},"products":["spinnaker"],"published":"2022-01-04","related":[{"cvss_score":10,"headline":"Spinnaker: RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths","id":"CVE-2026-32604","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":10,"headline":"Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling","id":"CVE-2026-32613","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":8.8,"headline":"Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types","id":"CVE-2026-44795","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":8.8,"headline":"Code injection in Netflix Spinnaker","id":"CVE-2020-9301","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":7.9,"headline":"Spinnaker vulnerable to SSRF due to improper restrictions on http from user input","id":"CVE-2025-61916","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":7.5,"headline":"Spinnaker: Improper yaml processing on kustomize bake operations","id":"CVE-2026-55175","kev_date_added":null,"published":"2026-07-10"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["spinnaker"]},"summary":"Unauthenticated users can create and execute pipelines in Spinnaker if RBAC is not configured, allowing remote code execution and resource deployment.","url":"https://insights.sbomify.com/CVE-2021-43832/"}