https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 20:07:55 +0000 https://cve.radiocsirt.org/vuln/bit-drupal-2022-25275 <p><strong>Affected:</strong> Bitnami: drupal</p> <p>In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when generating derivative images using the image styles system. Access to a non-public file is checked only if it is stored in the &#34;private&#34; file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability. This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) $config[&#39;image.settings&#39;][&#39;allow_insecure_derivatives&#39;] or (Drupal 7) $conf[&#39;image_allow_insecure_derivatives&#39;] to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI. Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.</p> <p><strong>Affected:</strong> Bitnami: drupal</p> <p>In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when generating derivative images using the image styles system. Access to a non-public file is checked only if it is stored in the &#34;private&#34; file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability. This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) $config[&#39;image.settings&#39;][&#39;allow_insecure_derivatives&#39;] or (Drupal 7) $conf[&#39;image_allow_insecure_derivatives&#39;] to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI. Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.</p> https://cve.radiocsirt.org/vuln/bit-drupal-2022-25275 https://cve.radiocsirt.org/vuln/certfr-2022-avi-667 certfr-2022-avi-667 https://cve.radiocsirt.org/vuln/certfr-2022-avi-667 https://cve.radiocsirt.org/vuln/euvd-2026-213250 EUVD-2026-213250 https://cve.radiocsirt.org/vuln/euvd-2026-213250 https://cve.radiocsirt.org/vuln/fkie_cve-2022-25275 <p>In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when generating derivative images using the image styles system. Access to a non-public file is checked only if it is stored in the &#34;private&#34; file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability. This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) $config[&#39;image.settings&#39;][&#39;allow_insecure_derivatives&#39;] or (Drupal 7) $conf[&#39;image_allow_insecure_derivatives&#39;] to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI. Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.</p> <p>In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when generating derivative images using the image styles system. Access to a non-public file is checked only if it is stored in the &#34;private&#34; file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability. This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) $config[&#39;image.settings&#39;][&#39;allow_insecure_derivatives&#39;] or (Drupal 7) $conf[&#39;image_allow_insecure_derivatives&#39;] to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI. Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-25275 https://cve.radiocsirt.org/vuln/ghsa-xh3v-6f9j-wxw3 <p><strong>Affected:</strong> Packagist: drupal/core</p> <p>In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when generating derivative images using the image styles system.</p> <p>Access to a non-public file is checked only if it is stored in the &#34;private&#34; file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability.</p> <p>This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) `$config[&#39;image.settings&#39;][&#39;allow_insecure_derivatives&#39;]` or (Drupal 7) `$conf[&#39;image_allow_insecure_derivatives&#39;]` to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI.</p> <p>Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.</p> <p><strong>Affected:</strong> Packagist: drupal/core</p> <p>In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when generating derivative images using the image styles system.</p> <p>Access to a non-public file is checked only if it is stored in the &#34;private&#34; file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability.</p> <p>This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) `$config[&#39;image.settings&#39;][&#39;allow_insecure_derivatives&#39;]` or (Drupal 7) `$conf[&#39;image_allow_insecure_derivatives&#39;]` to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI.</p> <p>Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.</p> https://cve.radiocsirt.org/vuln/ghsa-xh3v-6f9j-wxw3 https://cve.radiocsirt.org/vuln/gsd-2022-25275 gsd-2022-25275 https://cve.radiocsirt.org/vuln/gsd-2022-25275 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-25275 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: drupal7, Ubuntu:Pro:16.04:LTS: drupal7</p> <p>In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when generating derivative images using the image styles system. Access to a non-public file is checked only if it is stored in the &#34;private&#34; file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability. This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) $config[&#39;image.settings&#39;][&#39;allow_insecure_derivatives&#39;] or (Drupal 7) $conf[&#39;image_allow_insecure_derivatives&#39;] to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI. Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: drupal7, Ubuntu:Pro:16.04:LTS: drupal7</p> <p>In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when generating derivative images using the image styles system. Access to a non-public file is checked only if it is stored in the &#34;private&#34; file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability. This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) $config[&#39;image.settings&#39;][&#39;allow_insecure_derivatives&#39;] or (Drupal 7) $conf[&#39;image_allow_insecure_derivatives&#39;] to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI. Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-25275