CVE-2021-43832
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpinnaker 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSpinnaker's Gate service has an improper authorization vulnerability allowing any user with network access to create and execute pipelines without authentication. This bypasses all access controls when RBAC is not enabled, permitting arbitrary resource deployment across any configured cloud account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.25.8>= 1.26.0, < 1.26.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Spinnaker versionCheck the version of the Spinnaker installation via 'hal version list' or inspect the halyard/deck/gate pods/images, or look at the version file in the Spinnaker deploymentAffected if Installed version is < 1.25.8 or >= 1.26.0 but < 1.26.7
-
Locate the Gate service configurationFind the Gate service endpoint configuration in halyard settings or Kubernetes services, typically on port 8084 for API accessAffected if Gate service is network-accessible without authentication controls
-
Check if RBAC is enabledInspect the Spinnaker configuration (halyard config) or Kubernetes configmaps for 'security.authn' settings, specifically look for 'rbac' or 'authorization' mode configurationAffected if RBAC is disabled or not configured for the Gate service
-
Verify authentication is required for pipeline operationsTest unauthenticated access to Gate API endpoints (e.g., /pipelines endpoint) or inspect the security settings in halyard under 'security.auth' configurationAffected if Pipeline creation and execution endpoints accept requests without requiring valid authentication tokens
-
Confirm cloud account access without authorizationAttempt to access cloud provider account configuration through Gate API without credentials, or review the 'accounts' configuration to verify authorization is enforcedAffected if Any configured cloud account can be accessed or used for resource deployment without RBAC enforcement
You are affected if Spinnaker version is in the vulnerable range AND Gate service is network-accessible AND RBAC is disabled or not properly configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.25.81.26.7
Upgrade to the patched version immediately. If upgrading is not possible, enable RBAC on ALL accounts and applications, block application access unless permissions are configured, and restrict application creation using appropriate wildcards.
Spinnaker 1.25.8+ or 1.26.7+ (latest patch version in respective branch)
- Upgrade Spinnaker to version 1.25.8 or later if running version 1.25.x
- Upgrade Spinnaker to version 1.26.7 or later if running version 1.26.x
- If unable to upgrade immediately, enable Role-based access control (RBAC) on ALL accounts and applications within Spinnaker
- Configure Spinnaker to block application access unless permissions are properly enabled
- Restrict ALL application creation using appropriate wildcards in the configuration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43832 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-43832 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data