CVE-2024-43784 json
Re-creating a deleted user in lakeFS will re-enable previous user credentials that existed prior to it's deletion
published last yr. modified 4mo ago also EUVD-2024-3356 , GHSA-hh33-46q4-hwm2 , GO-2024-3291
- cvss
- 5.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
lakeFS is an open-source tool that transforms object storage into a Git-like repository. Existing lakeFS users who have issued credentials to users who have been deleted are affected by this vulnerability. When creating a new user with the same username as a deleted user, that user will inherit all of the previous user's credentials. This issue has been addressed in release version 1.33.0 and all users are advised to upgrade. The only known workaround for those who cannot upgrade is to not reuse usernames.
Patch / fix
- go github.com/treeverse/lakefs 1.33.0
- lakefs lakefs 1.33.0
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20241209T183251-1.1
opensuse advisories openSUSE-SU-2024:14567-1
Is CVE-2024-43784 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L |
| GitHub | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/treeverse/lakefs | <1.33.0 |
1.33.0 |
Affected products
- treeverse lakeFS
Classification
References
Sources
- CVE List CVE-2024-43784
- GitHub Advisory GHSA-hh33-46q4-hwm2
- NVD CVE-2024-43784
- OSV GO-2024-3291
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.