Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/vulndb: potential Go vuln in github.com/treeverse/lakefs: GHSA-j7jw-28jm-whr6 #3479

Open
GoVulnBot opened this issue Feb 21, 2025 · 0 comments

Comments

@GoVulnBot
Copy link

Advisory GHSA-j7jw-28jm-whr6 references a vulnerability in the following Go modules:

Module
github.com/treeverse/lakefs

Description:

Impact

An authenticated user can crash lakeFS by exhausting server memory. This is an authenticated denial-of-service issue.

Patches

This problem has been patched and exists in versions 1.49.1 and below

Workarounds

On S3 backends, configure

# ...
blockstore:
  s3:
    disable_pre_signed_multipart: true

or set environment variable LAKEFS_BLOCKSTORE_S3_DISABLE_PRE_SIGNED_MULTIPART to true.

References

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

References:

Cross references:

See doc/quickstart.md for instructions on how to triage this report.

id: GO-ID-PENDING
modules:
    - module: github.com/treeverse/lakefs
      versions:
        - fixed: 1.50.0
      vulnerable_at: 1.49.1
summary: lakeFS allows an authenticated user to cause a crash by exhausting server memory in github.com/treeverse/lakefs
cves:
    - CVE-2025-27100
ghsas:
    - GHSA-j7jw-28jm-whr6
references:
    - advisory: https://github.com/advisories/GHSA-j7jw-28jm-whr6
    - advisory: https://github.com/treeverse/lakeFS/security/advisories/GHSA-j7jw-28jm-whr6
    - advisory: https://nvd.nist.gov/vuln/detail/CVE-2025-27100
    - fix: https://github.com/treeverse/lakeFS/commit/3a625752acdf3f8e137bec20451e71d0f9fa82f2
source:
    id: GHSA-j7jw-28jm-whr6
    created: 2025-02-21T22:01:26.022574398Z
review_status: UNREVIEWED

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant