Summary
Venice vulnerable to Partial Path Traversal issue within the functions load-file and load-resource
Impact
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.16 are affected by this issue.
Patches
Upgrade to Venice >= 1.10.17, if you are on a version < 1.10.17
Workarounds
If you cannot upgrade the library, you can control the functions that can be used in Venice with a sandbox. If it is appropriate, the functions load-file and load-resource can be blacklisted in the sandbox.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in GitHub Venice
- Email us at juerg.ch
Credits
I want to publicly recognize the contribution of Jonathan Leitschuh for reporting this issue.
Impact
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
CVE-2022-36007 has a CVSS score of 6.1 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.10.17); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2022-36007? CVE-2022-36007 is a medium-severity path traversal vulnerability in com.github.jlangch:venice (maven), affecting versions <= 1.10.16. It is fixed in 1.10.17. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- How severe is CVE-2022-36007? CVE-2022-36007 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of com.github.jlangch:venice are affected by CVE-2022-36007? com.github.jlangch:venice (maven) versions <= 1.10.16 is affected.
- Is there a fix for CVE-2022-36007? Yes. CVE-2022-36007 is fixed in 1.10.17. Upgrade to this version or later.
- Is CVE-2022-36007 exploitable, and should I be worried? Whether CVE-2022-36007 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-36007 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-36007? Upgrade
com.github.jlangch:veniceto 1.10.17 or later.