<?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>Fri, 02 Oct 2026 19:48:41 +0000</lastBuildDate>
    <item>
      <title>cnvd-2017-32442</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2017-32442</link>
      <description>cnvd-2017-32442</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2017-32442</guid>
    </item>
    <item>
      <title>EUVD-2026-168362</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-168362</link>
      <description>EUVD-2026-168362</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-168362</guid>
    </item>
    <item>
      <title>fkie_cve-2017-3163</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2017-3163</link>
      <description>&lt;p&gt;When using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2017-3163</guid>
    </item>
    <item>
      <title>GHSA-387v-84cv-9qmc — Improper Limitation of a Pathname ('Path Traversal') in org.apache.solr:solr-core</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-387v-84cv-9qmc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.solr:solr-core&lt;/p&gt;
&lt;p&gt;When using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.solr:solr-core&lt;/p&gt;
&lt;p&gt;When using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-387v-84cv-9qmc</guid>
    </item>
    <item>
      <title>gsd-2017-3163</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2017-3163</link>
      <description>gsd-2017-3163</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2017-3163</guid>
    </item>
    <item>
      <title>RHSA-2018:1447 — Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.20 security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2018:1447</link>
      <description>&lt;p&gt;Artemis: Deserialization of untrusted input vulnerability solr: Directory traversal via Index Replication HTTP API jackson-databind: Unsafe deserialization due to incomplete black list (incomplete fix for CVE-2017-7525) jackson-databind: Unsafe deserialization due to incomplete black list (incomplete fix for CVE-2017-15095) tomcat: Incorrect handling of empty string URL in security constraints can lead to unintended exposure of resources jackson-databind: incomplete fix for CVE-2017-7525 permits unsafe serialization via c3p0 libraries slf4j: Deserialisation vulnerability in EventData constructor can allow for arbitrary code execution&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Artemis: Deserialization of untrusted input vulnerability solr: Directory traversal via Index Replication HTTP API jackson-databind: Unsafe deserialization due to incomplete black list (incomplete fix for CVE-2017-7525) jackson-databind: Unsafe deserialization due to incomplete black list (incomplete fix for CVE-2017-15095) tomcat: Incorrect handling of empty string URL in security constraints can lead to unintended exposure of resources jackson-databind: incomplete fix for CVE-2017-7525 permits unsafe serialization via c3p0 libraries slf4j: Deserialisation vulnerability in EventData constructor can allow for arbitrary code execution&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2018:1447</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2017-3163</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-3163</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: lucene-solr, Ubuntu:Pro:16.04:LTS: lucene-solr&lt;/p&gt;
&lt;p&gt;When using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: lucene-solr, Ubuntu:Pro:16.04:LTS: lucene-solr&lt;/p&gt;
&lt;p&gt;When using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2017-3163</guid>
    </item>
  </channel>
</rss>
