NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

lakeFS vulnerable to Arbitrary JavaScript Injection via Direct Link to HTML FilesGHSA-9phh-r37v-34wh

MEDIUMFix: treeverse/lakeFS@2b2a9fa

GHSA-9phh-r37v-34wh is a medium-severity (CVSS 5.8) vulnerability in github.com/treeverse/lakefs. A fix is available for github.com/treeverse/lakefs — see the affected versions and patch details below.

Also known asGO-2023-2012
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Aug 21, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/treeverse/lakefsall versions0.106.0go get github.com/treeverse/lakefs@v0.106.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/treeverse/lakefs to 0.106.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9phh-r37v-34wh 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.

Frequently Asked Questions

### 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.
O3 Security · Impact-Aware SCA

Is GHSA-9phh-r37v-34wh in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
lakeFS vulnerable to Arbitrary JavaScript Injection via…