# GO-2024-3293: Full access to the host's OS file system using osfs.FS with Router.Static in goyave.dev/goyave/v5

> Attackers can read arbitrary host files via path traversal in static file serving, requiring developers to switch to embedded filesystems.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Dec 2024

## What is GO-2024-3293?

GO-2024-3293 is a path traversal vulnerability in goyave.dev/goyave/v5, published on 13 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Static file serving using router.Static and osfs.FS allows clients to access any file on the host file system using relative paths because the requested path is not sanitized and . and .. segments are accepted. The files will be returned as a response, provided the system user running the Go application has read access to the requested file.

As a workaround, use fsutil.NewEmbed(embeddedFS) from the goyave.dev/goyave/v5/util/fsutil package to serve static content using Router.Static instead of &osfs.FS. Embedded file systems are rooted to the specified directory, making it impossible to navigate outside of the developers' intended directory.

## Which versions are affected by GO-2024-3293?

1 open source package ship an affected version, including goyave.dev/goyave/v5.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `goyave.dev/goyave/v5` | Go | From 5.0.0 | 5.5.0 |

## How do I fix GO-2024-3293?

Upgrade goyave.dev/goyave/v5 to 5.5.0 or later.

## Is GO-2024-3293 being exploited?

There is no known exploitation of GO-2024-3293 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GO-2024-3293 and fix it if it is affected.

What it is: GO-2024-3293 is a path traversal vulnerability in goyave.dev/goyave/v5, published on 13 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GO-2024-3293 in the wild and no public exploit code.

Affected packages and fixed versions:
- goyave.dev/goyave/v5 (Go): affected from 5.0.0; fixed in 5.5.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GO-2024-3293/ (Markdown: https://insights.sbomify.com/GO-2024-3293/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GO-2024-3293

---
From sbomify Insights: https://insights.sbomify.com/GO-2024-3293/
Summaries are generated and may contain mistakes; the official description above is the record.