Skip to content
Fencer Intel
medium 5.8

GHSA-9phh-r37v-34wh json

lakeFS vulnerable to Arbitrary JavaScript Injection via Direct Link to HTML Files

published 3y ago modified 8mo ago also GO-2023-2012

cvss
5.8
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact The browser renders the resulting HTML when opening a direct link to an HTML file via lakeFS. Any JavaScript within that page is executed within the context of the domain lakeFS is running in. An attacker can inject a malicious script inline, download resources from another domain, or make arbitrary HTTP requests. This would allow the attacker to send information to a random domain or carry out lakeFS operations while impersonating the victim.

Note that to carry out this attack, an attacker must already have access to upload the malicious HTML file to one or more repositories. It also depends on the victim receiving and opening the link to the malicious HTML file.

### Patches This is fixed in lakeFS version 0.106.0

### Workarounds There are no known workarounds at this time.

Patch / fix

  • go github.com/treeverse/lakefs 0.106.0

Is GHSA-9phh-r37v-34wh 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 Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 5.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/treeverse/lakefs
<0.106.0
0.106.0

References

Sources

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.