Em resumo
- CVE-2023-39348 é uma vulnerabilidade MÉDIO (CVSS 5.3) que afeta github.com/spinnaker/spinnaker, spinnaker (linuxfoundation).
- Chance de exploração nos próximos 30 dias (EPSS): 0.38%, maior que 32.1% das vulnerabilidades.
- Correção: atualize para 1.29.6, 1.30.3, 1.28.8 ou posterior.
| Package | Affected versions | Patched versions |
|---|
| github.com/spinnaker/spinnaker Go | ≥ 1.29.0≥ 1.30.0≥ 1.31.0all versions
| No fix yet |
| spinnaker | = 1.30.0≥ 1.29.0, < 1.29.6≥ 1.30.0, < 1.30.3< 1.28.8
| 1.29.61.30.31.28.8
|
Description
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
NVD description
Spinnaker is an open source, multi-cloud continuous delivery platform. 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. This only affects users of GitHub Status Notifications. This issue has been addressed in pull request 1316. Users are advised to upgrade. Users unable to upgrade should disable GH Status Notifications, Filter their logs for Echo log data and use read-only tokens that are limited in scope.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free