<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T23:13:09.806426+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-5789-5fc7-67v3</id>
    <title>GHSA-5789-5fc7-67v3 — Jupyter Server: Path Traversal via incorrect startswith() root directory check allows access to sibling directories</title>
    <updated>2026-09-30T23:13:09.808568+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: jupyter-server</p>
<p>### Summary</p>
<p>Jupyter Server &lt;=2.17.0 can access directories sibling to the root directory, if it starts with the root dir's name.</p>
<p>### PoC</p>
<p>Minimal:</p>
<p>```
.
├── test/              &lt;- root directory.
│   └── test.txt
└── testtest/
    └── secret.txt     &lt;- file to exfiltrate that we should not be able to access via API
```</p>
<p>```bash
HOST="http://localhost:8888"
TOKEN=""
SIBLING="testtest"
TARGET="secret.txt"</p>
<p>curl -s -X POST \
  "$HOST/api/contents/%2e%2e/$SIBLING/$TARGET/checkpoints" \
  -H "Authorization: token $TOKEN"
```</p>
<p>Full PoC by @stef41: https://gist.github.com/Yann-P/66d4982a965dee8fcb8dd89db29e7006</p>
<p>### Impact</p>
<p>It is possible for an authenticated user to access content outside the server's `root_dir` in siblings directories sharing the same prefix as the `root_dir`. The attacker can escalate access, reading, writing, and deleting from sibling directories.</p>
<p>This can have a tangible impact for deployments using predictable naming scheme with multi-tenant server, for example `user1`, `user2`, `user3`, ..., `user10` etc, as `user1` could access and modify files of all `user10` - `user19` and higher.</p>
<p>In a hypothetical system where users can choose a name of their folder, an attacker could choose a single-letter username to gain access to a significant number of sibling directories.</p>
<p>### Workarounds</p>
<p>Use folder names that do not overlap.</p>
<p>### Acknowledgments</p>
<p>Thank you to @stef41 for providing a useful PoC.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-5789-5fc7-67v3"/>
  </entry>
</feed>
