Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-28q9-9c3g-v3f9

lakeFS vulnerable to authenticated users deleting files they are not authorized to delete

Also known asGO-2022-1019
Published
Sep 23, 2022
Updated
Aug 21, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
🐹github.com/treeverse/lakefs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Authenticated users can send a request to delete-objects through the s3 gateway and delete files they are not authorized to delete.

Patches

lakeFS v0.82.0 and later

Workarounds

Drop specific request to the lakeFS listen port. Any request with "Authorization" header and value that starts with "AWS".

References

advisories/GHSA-28q9-9c3g-v3f9

For more information

If you have any questions or comments about this advisory:

Ask on the lakeFS Slack #help channel Email us at [email protected]

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/treeverse/lakefsall versions0.82.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/treeverse/lakefs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/treeverse/lakefs to 0.82.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-28q9-9c3g-v3f9 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-28q9-9c3g-v3f9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-28q9-9c3g-v3f9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Authenticated users can send a request to delete-objects through the s3 gateway and delete files they are not authorized to delete. ### Patches lakeFS v0.82.0 and later ### Workarounds Drop specific request to the lakeFS listen port. Any request with "Authorization" header and value that starts with "AWS". ### References [advisories/GHSA-28q9-9c3g-v3f9](https://github.com/treeverse/lakeFS/security/advisories/GHSA-28q9-9c3g-v3f9) ### For more information If you have any questions or comments about this advisory: Ask on the [lakeFS Slack](https://github.com/treeverse/lakeFS/s
O3 Security · Impact-Aware SCA

Is GHSA-28q9-9c3g-v3f9 in your dependencies?

O3 detects GHSA-28q9-9c3g-v3f9 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.