CVE-2022-23506

Spinnaker's Rosco microservice vulnerable to improper log masking on AWS Packer builds

HIGH

7.5

CVSS Score

Published: January 3, 2023 at 08:04 PM UTC

Updated: June 17, 2026 at 04:30 AM UTC

2 products affected across 2 vendorsSpinnakerSpinnaker

Using spinnaker by spinnaker?

Get instant alerts when new vulnerabilities affect spinnaker - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.5

Exploit prediction

EPSS 0.6%

SSVC

No known exploit

Description

Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes, and Spinnaker's Rosco microservice produces machine images. Rosco prior to versions 1.29.2, 1.28.4, and 1.27.3 does not property mask secrets generated via packer builds. This can lead to exposure of sensitive AWS credentials in packer log files. Versions 1.29.2, 1.28.4, and 1.27.3 of Rosco contain fixes for this issue. A workaround is available. It's recommended to use short lived credentials via role assumption and IAM profiles. Additionally, credentials can be set in `/home/spinnaker/.aws/credentials` and `/home/spinnaker/.aws/config` as a volume mount for Rosco pods vs. setting credentials in roscos bake config properties. Last even with those it's recommend to use IAM Roles vs. long lived credentials. This drastically mitigates the risk of credentials exposure. If users have used static credentials, it's recommended to purge any bake logs for AWS, evaluate whether AWS_ACCESS_KEY, SECRET_KEY and/or other sensitive data has been introduced in log files and bake job logs. Then, rotate these credentials and evaluate potential improper use of those credentials.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Spinnaker · Linuxfoundation

95%

v < 1.27.31.28.0 ≤ v < 1.28.41.29.0 ≤ v < 1.29.2

Affected range stops below 1.27.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.28.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.29.2, so it looks safe — our inference, not a vendor statement

Spinnaker · Spinnaker

60%

v < 1.27.3v < 1.28.4v < 1.29.2

Affected range stops below 1.27.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.28.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.29.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

x_refsource_MISCPatchThird Party Advisory

Source: [email protected]

https://github.com/spinnaker/rosco/commit/e80cfaa1abfb3a0e9026d45d6027291bfb815daf

x_refsource_CONFIRMMitigationThird Party Advisory

Source: [email protected]

https://github.com/spinnaker/spinnaker/security/advisories/GHSA-2233-cqj8-j2q5

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGH[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: NONE
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-532

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card