GHSA-459f-x8vq-xjjm
GHSA-459f-x8vq-xjjm is a CWE-61 vulnerability in static-web-server. O3 Security confirms whether GHSA-459f-x8vq-xjjm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Static Web Server vulnerable to a symbolic link path traversal
Blast Radius
static-web-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Symbolic links (symlinks) could be used to access files or directories outside the intended web root folder.
Details
SWS generally does not prevent symlinks from escaping the web server’s root directory. Therefore, if a malicious actor gains access to the web server’s root directory, they could create symlinks to access other files outside the designated web root folder either by URL or via the directory listing.
PoC
- Serve a directory (web root) with SWS.
- Create a symlink inside the web root that points to a file outside the web root.
e.g.
ln -s escape.txt $HOME/.bashrc - Open
http://localhost/escape.txtin your browser. - The file content will be served.
Impact
Any web server that runs with elevated privileges (e.g., root/administrator) and handles user-supplied file uploads is primarily impacted.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | static-web-server | all versions | 2.40.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for static-web-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update static-web-server to 2.40.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-459f-x8vq-xjjm is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-459f-x8vq-xjjm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-459f-x8vq-xjjm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-459f-x8vq-xjjm in your dependencies?
O3 detects GHSA-459f-x8vq-xjjm across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.