CVE-2022-36007 Partial Path Traversal in com.github.jlangch:venice
Attackers can read files outside configured load paths if absolute paths share a prefix with allowed directories, affecting Venice library users.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-36007?
CVE-2022-36007 is a medium-severity path traversal vulnerability in jlangch venice, published on 14 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Venice is a Clojure inspired sandboxed Lisp dialect with excellent Java interoperability. A partial path traversal issue exists within the functions `load-file` and `load-resource`. These functions can be limited to load files from a list of load paths. Assuming Venice has been configured with the load paths: `[ "/Users/foo/resources" ]` When passing **relative** paths to these two vulnerable functions everything is fine: `(load-resource "test.png")` => loads the file "/Users/foo/resources/test.png" `(load-resource "../resources-alt/test.png")` => rejected, outside the load path When passing **absolute** paths to these two vulnerable functions Venice may return files outside the configured load paths: `(load-resource "/Users/foo/resources/test.png")` => loads the file "/Users/foo/resources/test.png" `(load-resource "/Users/foo/resources-alt/test.png")` => loads the file "/Users/foo/resources-alt/test.png" !!! The latter call suffers from the _Partial Path Traversal_ vulnerability. This issue’s scope is limited to absolute paths whose name prefix matches a load path. E.g. for a load-path `"/Users/foo/resources"`, the actor can cause loading a resource also from `"/Users/foo/resources-alt"`, but not from `"/Users/foo/images"`. Versions of Venice before and including v1.10.17 are affected by this issue. Upgrade to Venice >= 1.10.18, if you are on a version < 1.10.18. There are currently no known workarounds.
Weakness: CWE-22
Which versions are affected by CVE-2022-36007?
2 open source packages ship an affected version, including com.github.jlangch:venice. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
com.github.jlangch:venice Maven | All versions | 1.10.17 |
com.github.jlangch:venice Maven | All versions | 1.10.17 |
Products include Venice Project Venice.
How do I fix CVE-2022-36007?
Upgrade com.github.jlangch:venice to 1.10.17 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2022-36007 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36007 exists.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-4mmh-5vw7-rgvj.