{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23506 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-23506 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23506 is a medium-severity vulnerability in spinnaker, published on 3 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23506 and fix it if it is affected.\n\nWhat it is: CVE-2022-23506 is a medium-severity vulnerability in spinnaker, published on 3 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-23506 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-2022-23506/ (Markdown: https://insights.sbomify.com/CVE-2022-23506/index.md)","id":"CVE-2022-23506","markdown":"https://insights.sbomify.com/CVE-2022-23506/index.md","name":"CVE-2022-23506","record":{"aliases":["GHSA-2233-cqj8-j2q5"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Spinnaker Rosco microservice","requires_auth":"low_privilege","summary":"Attackers can read sensitive AWS credentials from unmasked Packer build logs in Spinnaker Rosco, potentially leading to cloud account compromise.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"spinnaker","vendor":"linuxfoundation"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.\n\nA 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Spinnaker's Rosco microservice vulnerable to improper log masking on AWS Packer builds","id":"CVE-2022-23506","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Light client verification not taking into account chain ID","id":"CVE-2022-23507"},"packages":[],"prev":{"headline":"Passport-wsfed-saml2 vulnerable to Authentication Bypass for WSFed authentication","id":"CVE-2022-23505"},"products":["spinnaker"],"published":"2023-01-03","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":10,"headline":"Improper Access Control in spinnaker","id":"CVE-2021-43832","kev_date_added":null,"published":"2022-01-04"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["spinnaker"]},"summary":"Attackers can read sensitive AWS credentials from unmasked Packer build logs in Spinnaker Rosco, potentially leading to cloud account compromise.","url":"https://insights.sbomify.com/CVE-2022-23506/"}