<?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>Tue, 06 Oct 2026 02:16:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-45217 — Apache Solr: ConfigSets created during a backup restore command are trusted implicitly</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-45217</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Solr, apache_software_foundation apache_solr&lt;/p&gt;
&lt;p&gt;Insecure Default Initialization of Resource vulnerability in Apache Solr.&lt;/p&gt;
&lt;p&gt;New ConfigSets that are created via a Restore command, which copy a configSet from the backup and give it a new name, are created without setting the &amp;#34;trusted&amp;#34; metadata.
ConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to &amp;#34;trusted&amp;#34; ConfigSets that may not have been created with an Authenticated request.
&amp;#34;trusted&amp;#34; ConfigSets are able to load custom code into classloaders, therefore the flag is supposed to only be set when the request that uploads the ConfigSet is Authenticated &amp;amp; Authorized.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Solr: from 6.6.0 before 8.11.4, from 9.0.0 before 9.7.0. This issue does not affect Solr instances that are secured via Authentication/Authorization.&lt;/p&gt;
&lt;p&gt;Users are primarily recommended to use Authentication and Authorization when running Solr. However, upgrading to version 9.7.0, or 8.11.4 will mitigate this issue otherwise.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Solr, apache_software_foundation apache_solr&lt;/p&gt;
&lt;p&gt;Insecure Default Initialization of Resource vulnerability in Apache Solr.&lt;/p&gt;
&lt;p&gt;New ConfigSets that are created via a Restore command, which copy a configSet from the backup and give it a new name, are created without setting the &amp;#34;trusted&amp;#34; metadata.
ConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to &amp;#34;trusted&amp;#34; ConfigSets that may not have been created with an Authenticated request.
&amp;#34;trusted&amp;#34; ConfigSets are able to load custom code into classloaders, therefore the flag is supposed to only be set when the request that uploads the ConfigSet is Authenticated &amp;amp; Authorized.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Solr: from 6.6.0 before 8.11.4, from 9.0.0 before 9.7.0. This issue does not affect Solr instances that are secured via Authentication/Authorization.&lt;/p&gt;
&lt;p&gt;Users are primarily recommended to use Authentication and Authorization when running Solr. However, upgrading to version 9.7.0, or 8.11.4 will mitigate this issue otherwise.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-45217</guid>
    </item>
  </channel>
</rss>
