{"id":"CVE-2024-45217","aliases":["BIT-solr-2024-45217","EUVD-2024-3053","GHSA-h7w9-c5vx-x7j3","UBUNTU-CVE-2024-45217"],"status":"published","title":"Apache Solr: ConfigSets created during a backup restore command are trusted implicitly","description":"Insecure Default Initialization of Resource vulnerability in Apache Solr.\n\nNew 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 \"trusted\" metadata.\nConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to \"trusted\" ConfigSets that may not have been created with an Authenticated request.\n\"trusted\" 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 \u0026 Authorized.\n\nThis 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.\n\nUsers 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.","severity":{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"high","assessor":"adp","from":"cve"},"epss":{"day":"2026-11-09","score":0.00748,"percentile":0.55168,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-1188"],"published":"2024-10-16T07:51:16Z","modified":"2026-10-28T02:31:10Z","fixes":[{"ecosystem":"Maven","package":"org.apache.solr:solr","fixed_in":["8.11.4","9.7.0"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"solr","fixed_in":["8.11.4","9.7.0"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.apache.solr:solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.0"},{"fixed":"8.11.4"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.solr:solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.0.0"},{"fixed":"9.7.0"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"solr","ranges":[{"type":"SEMVER","events":[{"introduced":"6.6.0"},{"fixed":"8.11.4"},{"introduced":"9.0.0"},{"fixed":"9.7.0"}]}]},{"source":"osv","ecosystem":"Maven","package":"org.apache.solr:solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.0"},{"fixed":"8.11.4"}]}]},{"source":"osv","ecosystem":"Maven","package":"org.apache.solr:solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"9.0.0"},{"fixed":"9.7.0"}]}]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"lucene-solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.2+dfsg-1","3.6.2+dfsg-2","3.6.2+dfsg-2ubuntu0.1~esm1","3.6.2+dfsg-2ubuntu0.1~esm2","3.6.2+dfsg-2ubuntu0.1~esm4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"lucene-solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.2+dfsg-7","3.6.2+dfsg-8","3.6.2+dfsg-8ubuntu0.1","3.6.2+dfsg-8ubuntu0.1+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"lucene-solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.2+dfsg-10","3.6.2+dfsg-11","3.6.2+dfsg-18~18.04","3.6.2+dfsg-18~18.04.1~esm2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"lucene-solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.2+dfsg-20","3.6.2+dfsg-22"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"lucene-solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.2+dfsg-24"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"lucene-solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.2+dfsg-26"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"lucene-solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.2+dfsg-26"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"lucene-solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.2+dfsg-27"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"lucene-solr","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.6.2+dfsg-26","3.6.2+dfsg-27"]}],"products":[{"vendor":"apache","product":"solr"},{"vendor":"apache software foundation","product":"apache solr"},{"vendor":"apache_software_foundation","product":"apache_solr"}],"references":[{"url":"https://solr.apache.org/security.html#cve-2024-45217-apache-solr-configsets-created-during-a-backup-restore-command-are-trusted-implicitly","tags":["vendor-advisory","Vendor Advisory","advisory","web","report"]},{"url":"http://www.openwall.com/lists/oss-security/2024/10/15/9","tags":["Mailing List","discussion","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45217","tags":["web","advisory"]},{"url":"https://issues.apache.org/jira/browse/SOLR-17418","tags":["web"]},{"url":"https://github.com/advisories/GHSA-h7w9-c5vx-x7j3"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/45xxx/CVE-2024-45217.json","tags":["advisory"]},{"url":"http://svn.apache.org/viewvc/lucene/dev/branches/branch_4x/solr/webapp","tags":["package"]},{"url":"https://ubuntu.com/security/CVE-2024-45217","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-45217","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2024-45217","title":"Apache Solr: ConfigSets created during a backup restore command are trusted implicitly","description":"Insecure Default Initialization of Resource vulnerability in Apache Solr.\n\nNew 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 \"trusted\" metadata.\nConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to \"trusted\" ConfigSets that may not have been created with an Authenticated request.\n\"trusted\" 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 \u0026 Authorized.\n\nThis 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.\n\nUsers 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.","status":"published","published":"2024-10-16T07:51:16.558Z","modified":"2024-10-16T15:08:26.625Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"high","assessor":"adp"}],"cwes":["CWE-1188"],"updated_at":"2026-11-02T14:34:08.500935Z"}],"euvd":[{"id":"EUVD-2024-3053","description":"Insecure Default Initialization of Resource vulnerability in Apache Solr.\n\nNew 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 \"trusted\" metadata.\nConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to \"trusted\" ConfigSets that may not have been created with an Authenticated request.\n\"trusted\" 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 \u0026 Authorized.\n\nThis 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.\n\nUsers 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.","status":"published","published":"2024-10-16T07:51:16Z","modified":"2024-10-16T15:08:26Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-03T00:27:34.865484Z"}],"ghsa":[{"id":"GHSA-h7w9-c5vx-x7j3","title":"Insecure Default Initialization of Resource vulnerability in Apache Solr","description":"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 \"trusted\" metadata.\nConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to \"trusted\" ConfigSets that may not have been created with an Authenticated request.\n\"trusted\" 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 \u0026 Authorized.\n\nThis 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.\n\nUsers 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.","status":"published","published":"2024-10-16T09:30:31Z","modified":"2025-07-02T14:20:11Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-1188"],"updated_at":"2026-11-02T14:38:48.783737Z"}],"nvd":[{"id":"CVE-2024-45217","description":"Insecure Default Initialization of Resource vulnerability in Apache Solr.\n\nNew 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 \"trusted\" metadata.\nConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to \"trusted\" ConfigSets that may not have been created with an Authenticated request.\n\"trusted\" 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 \u0026 Authorized.\n\nThis 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.\n\nUsers 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.","status":"published","published":"2024-10-16T08:15:05.353Z","modified":"2026-06-17T07:53:48.227Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"high","assessor":"secondary"}],"cwes":["CWE-1188"],"updated_at":"2026-11-02T14:10:31.879321Z"}],"osv":[{"id":"CVE-2024-45217","title":"Apache Solr: ConfigSets created during a backup restore command are trusted implicitly","description":"Insecure Default Initialization of Resource vulnerability in Apache Solr.\n\nNew 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 \"trusted\" metadata.\nConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to \"trusted\" ConfigSets that may not have been created with an Authenticated request.\n\"trusted\" 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 \u0026 Authorized.\n\nThis 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.\n\nUsers 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.","status":"published","published":"2024-10-16T07:51:16.558Z","modified":"2026-10-28T02:31:10.932301994Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-1188"],"updated_at":"2026-11-02T15:44:42.790566Z"},{"id":"GHSA-h7w9-c5vx-x7j3","title":"Insecure Default Initialization of Resource vulnerability in Apache Solr","description":"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 \"trusted\" metadata.\nConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to \"trusted\" ConfigSets that may not have been created with an Authenticated request.\n\"trusted\" 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 \u0026 Authorized.\n\nThis 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.\n\nUsers 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.","status":"published","published":"2024-10-16T09:30:31Z","modified":"2025-07-02T14:20:10Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-1188"],"updated_at":"2026-11-02T15:46:48.920784Z"},{"id":"UBUNTU-CVE-2024-45217","description":"Insecure Default Initialization of Resource vulnerability in Apache Solr. 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 \"trusted\" metadata. ConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to \"trusted\" ConfigSets that may not have been created with an Authenticated request. \"trusted\" 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 \u0026 Authorized. 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. 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.","status":"published","published":"2024-10-16T08:15:00Z","modified":"2026-10-17T12:56:39.533794868Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T16:55:02.636559Z"},{"id":"BIT-solr-2024-45217","title":"Apache Solr: ConfigSets created during a backup restore command are trusted implicitly","description":"Insecure Default Initialization of Resource vulnerability in Apache Solr.\n\nNew 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 \"trusted\" metadata.\nConfigSets that do not contain the flag are trusted implicitly if the metadata is missing, therefore this leads to \"trusted\" ConfigSets that may not have been created with an Authenticated request.\n\"trusted\" 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 \u0026 Authorized.\n\nThis 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.\n\nUsers 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.","status":"published","published":"2024-10-18T07:18:24.823Z","modified":"2026-09-08T08:48:19.351818314Z","updated_at":"2026-11-02T15:28:35.111822Z"}]}}