GHSA-4RGC-5G6R-2RJF

S3 credentials are logged in plain text

S3Creds:{Key:AKIAIOSFODNN7EXAMPLE Secret:wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

appears as part of the log message:

time="2023-05-12T13:51:52Z" level=error msg="failed to perform diff" func="pkg/plugins/diff.(*Service).RunDiff" file="build/pkg/plugins/diff/service.go:124" error="rpc error: code = Canceled desc = stream terminated by RST_STREAM with error code: CANCEL" host="localhost:8000" method=GET operation_id=OtfDiff params="{TablePaths:{Left:{Ref:data_load@ Path:aggs/agg_variety/} Right:{Ref:data_load Path:aggs/agg_variety/} Base:{Ref: Path:}} S3Creds:{Key:AKIAIOSFODNN7EXAMPLE Secret:wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY Endpoint:http://0.0.0.0:8000} Repo:example}" path="/api/v1/repositories/example/otf/refs/data_load%40/diff/data_load?table_path=aggs%2Fagg_variety%2F&type=delta" request_id=d3b6fdc7-2544-4c12-8e05-376f16e35a80 service_name=rest_api type=delta user=docker

Discovered when investigating #5862

No

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

disable all logging?

References

Are there any links users can visit to find out more?

GHSA-4RGC-5G6R-2RJF has a CVSS score of 8.4 (High). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.101.0); upgrading removes the vulnerable code path.

Kodem intelligence

Has the problem been patched? What versions should users upgrade to?

1. What is GHSA-4RGC-5G6R-2RJF? GHSA-4RGC-5G6R-2RJF is a high-severity security vulnerability in github.com/treeverse/lakefs (go), affecting versions < 0.101.0. It is fixed in 0.101.0.
2. How severe is GHSA-4RGC-5G6R-2RJF? GHSA-4RGC-5G6R-2RJF has a CVSS score of 8.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/treeverse/lakefs are affected by GHSA-4RGC-5G6R-2RJF? github.com/treeverse/lakefs (go) versions < 0.101.0 is affected.
4. Is there a fix for GHSA-4RGC-5G6R-2RJF? Yes. GHSA-4RGC-5G6R-2RJF is fixed in 0.101.0. Upgrade to this version or later.
5. Is GHSA-4RGC-5G6R-2RJF exploitable, and should I be worried? Whether GHSA-4RGC-5G6R-2RJF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-4RGC-5G6R-2RJF is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-4RGC-5G6R-2RJF? Upgrade github.com/treeverse/lakefs to 0.101.0 or later.