# CVE-2021-43832: Improper Access Control in spinnaker

> Unauthenticated users can create and execute pipelines in Spinnaker if RBAC is not configured, allowing remote code execution and resource deployment.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jan 2022
- **Updated:** 23 Apr 2025

## What is CVE-2021-43832?

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.

### Official description

Spinnaker is an open source, multi-cloud continuous delivery platform. Spinnaker has improper permissions allowing pipeline creation & 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2021-43832?

It affects 1 product.


Products: Linuxfoundation Spinnaker.

## How do I fix CVE-2021-43832?

No fix has been published for CVE-2021-43832 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-43832 being exploited?

There is no known exploitation of CVE-2021-43832 in the wild and no public exploit code.

## Other vulnerabilities in spinnaker

- [CVE-2026-32604](https://insights.sbomify.com/CVE-2026-32604/): Spinnaker: RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths (critical 10.0)
- [CVE-2026-32613](https://insights.sbomify.com/CVE-2026-32613/): Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling (critical 10.0)
- [CVE-2026-44795](https://insights.sbomify.com/CVE-2026-44795/): Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types (high 8.8)
- [CVE-2020-9301](https://insights.sbomify.com/CVE-2020-9301/): Code injection in Netflix Spinnaker (high 8.8)
- [CVE-2025-61916](https://insights.sbomify.com/CVE-2025-61916/): Spinnaker vulnerable to SSRF due to improper restrictions on http from user input (high 7.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43832 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2021-43832 in the wild and no public exploit code.

Affected product: spinnaker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-43832/ (Markdown: https://insights.sbomify.com/CVE-2021-43832/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-43832
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-43832
- OSV: https://osv.dev/vulnerability/CVE-2021-43832

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-43832/
Summaries are generated and may contain mistakes; the official description above is the record.