build(deps): bump snowflake-prometheus-exporter to resolve CVE-2025-46327 in gosnowflake #3528
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description
This PR aims to get rid of CVE-2025-46327 / GHSA-6jgm-j7h2-2fqg in Alloy, which is regarding a race condition when checking access to Easy Logging configuration file in gosnowflake package. Once you using a SBOM-based scan against Alloy, it's reporting this vulnerability.
Since
github.com/snowflakedb/gosnowflake
is an indirect dependency ofgithub.com/grafana/snowflake-prometheus-exporter
, I went ahead and created grafana/snowflake-prometheus-exporter#28 - This was reviewed, tested and merged by the team of snowflake-prometheus-exporter.Afterwards I ran:
This results in an update of snowflake-prometheus-exporter from
v0.0.0-20240813124544
tov0.0.0-20250507154309
and also the needed update of gosnowflake fromv1.7.2
tov1.14.0
. To get rid of the risk of CVE-2025-46327 we need v1.13.0 or higher.