CWE
532
Advisory Published
Advisory Published
Updated

CVE-2023-39348: Improper log output when using GitHub Status Notifications in spinnaker

First published: Mon Aug 28 2023(Updated: )

### Impact ONLY IMPACTS those use GitHub Status Notifications Log output when updating GitHub status is improperly set to FULL always. It's recommended to apply the patch and rotate the GitHub token used for github status notifications. Given that this would output github tokens to a log system, the risk is slightly higher than a "low" since token exposure could grant elevated access to repositories outside of control. If using READ restricted tokens, the exposure is such that the token itself could be used to access resources otherwise restricted from reads. ### Patches Patch is in progress. https://github.com/spinnaker/echo/pull/1316 ### Workarounds Disable GH Status Notifications. Filter your logs for Echo log data. Use read-only tokens that are limited in scope. ### References sig-security in slack: https://spinnakerteam.slack.com/archives/CFN8F5UR2

Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
Linuxfoundation Spinnaker<1.28.8
Linuxfoundation Spinnaker>=1.29.0<1.29.6
Linuxfoundation Spinnaker>=1.30.0<1.30.3
Linuxfoundation Spinnaker=1.30.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the impact of CVE-2023-39348?

    The impact of CVE-2023-39348 is that log output when updating GitHub status is improperly set to FULL always, which could expose GitHub tokens to a log system.

  • How can I mitigate the impact of CVE-2023-39348?

    To mitigate the impact of CVE-2023-39348, it is recommended to apply the patch and rotate the GitHub token used for GitHub status notifications.

  • Which versions of Spinnaker are affected by CVE-2023-39348?

    The versions of Spinnaker affected by CVE-2023-39348 are 1.28.8 up to, but not including, 1.31.1.

  • Where can I find more information about CVE-2023-39348?

    More information about CVE-2023-39348 can be found at the following references: - [GitHub Security Advisory](https://github.com/spinnaker/spinnaker/security/advisories/GHSA-rq5c-hvw6-8pr7) - [NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-39348)

  • What is the severity rating of CVE-2023-39348?

    CVE-2023-39348 has a severity rating of 5.3 (Medium).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203