Read the docs
TI-2022-07565 Aliases CVE-2022-23506

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

Priority LOW 34CWE-532Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-532.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00587 48th percentileScored 2026-11-07
Fix Fixed spinnaker (spinnaker): 1.27.3, 1.28.4, 1.29.2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
spinnakerspinnakerbefore 1.27.3; 1.28.0 to before 1.28.4; 1.29.0 to before 1.29.21.27.3, 1.28.4, 1.29.2Patch availableCNA
  • spinnaker Vendorspinnaker Affected before 1.27.3; 1.28.0 to before 1.28.4; 1.29.0 to before 1.29.2 Fixed in 1.27.3, 1.28.4, 1.29.2 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:linuxfoundation:spinnaker:*:*:*:*:*:*:*:*before 1.27.3; 1.28.0 to before 1.28.4; 1.29.0 to before 1.29.2Vulnerablebackstage
  • cpe:2.3:a:linuxfoundation:spinnaker:*:*:*:*:*:*:*:* Versions before 1.27.3; 1.28.0 to before 1.28.4; 1.29.0 to before 1.29.2 Vulnerable ·backstage

Remediation

  • Fix · CNA spinnaker (spinnaker) Fixed in 1.27.3, 1.28.4, 1.29.2

Timeline

  1. 2026-10-02 Threatist record created from CVE-2022-23506

References

Patch 1

Advisory 1

  • TI-2021-16529 Path Traversal in spinnaker CVSS 3.1HIGH 7.1
  • TI-2021-19638 Improper Access Control in spinnaker CVSS 3.1CRITICAL 10.0
  • TI-2026-25122 Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling CVSS 3.1CRITICAL 10.0
  • TI-2026-25113 Improper input validation in spinnaker CVSS 3.1CRITICAL 10.0
  • TI-2026-32679 Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types CVSS 3.1HIGH 8.8
  • TI-2026-39859 Spinnaker: Improper yaml processing on kustomize bake operations CVSS 3.1HIGH 7.5
See all 9 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences