{"answers":{"affected":"2 open source packages ship an affected version, including com.github.jlangch:venice. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36007 exists.","fix":"Upgrade com.github.jlangch:venice to 1.10.17 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-36007 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36007 exists.\n\nAffected packages and fixed versions:\n- com.github.jlangch:venice (Maven): affected all versions; fixed in 1.10.17\n- com.github.jlangch:venice (Maven): affected all versions; fixed in 1.10.17\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-36007/ (Markdown: https://insights.sbomify.com/CVE-2022-36007/index.md)","id":"CVE-2022-36007","markdown":"https://insights.sbomify.com/CVE-2022-36007/index.md","name":"CVE-2022-36007","record":{"aliases":["GHSA-4mmh-5vw7-rgvj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Venice Lisp library","requires_auth":"low_privilege","summary":"Attackers can read files outside configured load paths if absolute paths share a prefix with allowed directories, affecting Venice library users.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"venice","vendor":"venice_project"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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\")` =\u003e loads the file \"/Users/foo/resources/test.png\" `(load-resource \"../resources-alt/test.png\")` =\u003e 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\")` =\u003e loads the file \"/Users/foo/resources/test.png\" `(load-resource \"/Users/foo/resources-alt/test.png\")` =\u003e 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 \u003e= 1.10.18, if you are on a version \u003c 1.10.18. There are currently no known workarounds.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2025-08-20","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-08-20T11:26:49Z","kind":"github_poc","ref":"https://github.com/shoucheng3/jlangch__venice_CVE-2022-36007_1-10-16","stars":0,"title":null}],"tier":"weaponised"},"has_fix":true,"headline":"Partial Path Traversal in com.github.jlangch:venice","id":"CVE-2022-36007","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2022"},"n_packages":2,"n_references":4,"next":{"headline":"Message length overflow in frontier","id":"CVE-2022-36008"},"packages":[{"ecosystem":"Maven","fixed":["1.10.17"],"introduced":["0"],"last_affected":[],"package":"com.github.jlangch:venice","purl":null,"source":"GHSA-4mmh-5vw7-rgvj"},{"ecosystem":"Maven","fixed":["1.10.17"],"introduced":["0"],"last_affected":[],"package":"com.github.jlangch:venice","purl":"pkg:maven/com.github.jlangch/venice","source":"GHSA-4mmh-5vw7-rgvj"}],"prev":{"headline":"Authenticated remote code execution due to insecure deserialization (GHSL-2022-063)","id":"CVE-2022-36006"},"products":["venice"],"published":"2022-08-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["jlangch"]},"summary":"Attackers can read files outside configured load paths if absolute paths share a prefix with allowed directories, affecting Venice library users.","url":"https://insights.sbomify.com/CVE-2022-36007/"}