<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 26 Oct 2026 21:06:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-36007 — Partial Path Traversal in com.github.jlangch:venice</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-36007</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; jlangch venice&lt;/p&gt;
&lt;p&gt;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: `[ &amp;#34;/Users/foo/resources&amp;#34; ]` When passing **relative** paths to these two vulnerable functions everything is fine: `(load-resource &amp;#34;test.png&amp;#34;)` =&amp;gt; loads the file &amp;#34;/Users/foo/resources/test.png&amp;#34; `(load-resource &amp;#34;../resources-alt/test.png&amp;#34;)` =&amp;gt; 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 &amp;#34;/Users/foo/resources/test.png&amp;#34;)` =&amp;gt; loads the file &amp;#34;/Users/foo/resources/test.png&amp;#34; `(load-resource &amp;#34;/Users/foo/resources-alt/test.png&amp;#34;)` =&amp;gt; loads the file &amp;#34;/Users/foo/resources-alt/test.png&amp;#34; !!! 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 `&amp;#34;/Users/foo/resources&amp;#34;`, the actor can cause loading a resource also from `&amp;#34;/Users/foo/resources-alt&amp;#34;`, but not from `&amp;#34;/Users/foo/images&amp;#34;`. Versions of Venice before and including v1.10.17 are affected by this issue. Upgrade to Venice &amp;gt;= 1.10.18, if you are on a version &amp;lt; 1.10.18. There are currently no known workarounds.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; jlangch venice&lt;/p&gt;
&lt;p&gt;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: `[ &amp;#34;/Users/foo/resources&amp;#34; ]` When passing **relative** paths to these two vulnerable functions everything is fine: `(load-resource &amp;#34;test.png&amp;#34;)` =&amp;gt; loads the file &amp;#34;/Users/foo/resources/test.png&amp;#34; `(load-resource &amp;#34;../resources-alt/test.png&amp;#34;)` =&amp;gt; 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 &amp;#34;/Users/foo/resources/test.png&amp;#34;)` =&amp;gt; loads the file &amp;#34;/Users/foo/resources/test.png&amp;#34; `(load-resource &amp;#34;/Users/foo/resources-alt/test.png&amp;#34;)` =&amp;gt; loads the file &amp;#34;/Users/foo/resources-alt/test.png&amp;#34; !!! 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 `&amp;#34;/Users/foo/resources&amp;#34;`, the actor can cause loading a resource also from `&amp;#34;/Users/foo/resources-alt&amp;#34;`, but not from `&amp;#34;/Users/foo/images&amp;#34;`. Versions of Venice before and including v1.10.17 are affected by this issue. Upgrade to Venice &amp;gt;= 1.10.18, if you are on a version &amp;lt; 1.10.18. There are currently no known workarounds.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-36007</guid>
    </item>
  </channel>
</rss>
