Skip to content
Noroxi
OSV ecosystem advisory

GHSA-fvv5-h29g-f6w5: User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository

MediumCVSS 5.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: github.com/treeverse/lakefs (Go) 1.12.1.

Low priority for now. Upgrade to github.com/treeverse/lakefs (Go) 1.12.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

### Impact A bug in permissions validation allows a user with the `ci:ReadAction` permission to skip read checks when copying an object. If they additionally have read and write permission to path in the repository, they can copy an otherwise unreadable object and read it. In order to be affected and exploitable, the following conditions must ALL occur on the same user: 1. `ci:ReadAction` enabled for the repository. Predefined policies RepoManagementRead and RepoManagementFullAccess allow this action. 2. `fs:ReadObject` and `fs:WriteObject` enabled for some path. 3. `fs:ReadObject` _not_ available for some path Such a user can use (1) to copy the unreadable object (3) to a path that they can read and write (2). At that point they can read the object copy. ### Patches Releases >= 1.12.1 fix this issue in lakeFS. ### Workarounds As a workaround, use RBAC to deny `ci:*` permissions to all users, or to all users who have limited read access. Many installations are unaffected: * **Installations using ACLs are _not_ affected.** This includes all OSS installations that have not implemented an external authorization server. We do not know of any OSS installations that have implemented such a server. ACLs that allow ci:ReadAction also allow reading repositories, so no capabilities are granted. * **Installations using RBAC that use only predefined policies with "all" ARNs ("*") are _not_ affected.** This includes **all installations that have not defined any new groups in RBAC.** In order to be affected, **installations using RBAC** must define users and simultaneous allow `ci:ReadAction` and disallow `fs:ReadObject` for some path. `ci:ReadAction` is available in policies RepoManagementReadAll and RepoManagementFullAccess. By default these actions are configured for groups Developers and above, for all repositories and paths. ### References * [lakeFS RBAC](https://docs.lakefs.io/reference/security/rbac.html)

Published
Feb 22, 2024
Updated
Jun 4, 2024
EPSS
—
CWE
—

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-fvv5-h29g-f6w5

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
Gogithub.com/treeverse/lakefs

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/treeverse/lakefsfrom 0.90.0 · before 1.12.11.12.1

Same product

Go: all records

Other highest-scoring records for the same primary product.

  • GHSA-4rgc-5g6r-2rjflakeFS logs S3 credentials in plain text
    33Monitor
  • GHSA-26hr-q2wp-rvc5User with permission to write actions can impersonate another user when auth token is configured in environment variable
    24Monitor
  • GHSA-9phh-r37v-34whlakeFS vulnerable to Arbitrary JavaScript Injection via Direct Link to HTML Files
    23Monitor

Published before and after this one in the same product

  • ← EarlierGHSA-m836-gxwq-j2pmOct 28, 2021 · Improper Access Control in github.com/treeverse/lakefs
    22Monitor
  • ← EarlierGHSA-28q9-9c3g-v3f9Sep 23, 2022 · lakeFS vulnerable to authenticated users deleting files they are not authorized to delete
    0Monitor
  • Later →GO-2024-2581Jun 4, 2024 · User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository in…
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/treeverse/lakefs1.12.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

osv

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records