In some situations, the Image module does not correctly check access to image files not stored in the standard public files directory when g

Summary

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 "private" 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['image.settings']['allow_insecure_derivatives'] or (Drupal 7) $conf['image_allow_insecure_derivatives'] 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.

Timeline

1. Apr 26, 2023, 12:00 AM UTCCVE published
2. Feb 3, 2025, 6:45 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Feb 3, 2025, 6:45 PM UTCRecord last updated

Affected versions

• Drupal Core

  From 9.4 · fixed in 9.4.3; From 9.3 · fixed in 9.3.19; From 7 · fixed in 7.91

• drupal/corePackagist

  From 7.0.0 · fixed in 7.91

• drupal/corePackagist

  From 8.0.0 · fixed in 9.3.19

• drupal/corePackagist

  From 9.4.0 · fixed in 9.4.3

• drupal/corePackagist

  From 8.0.0 · fixed in 9.3.19; From 9.4.0 · fixed in 9.4.3

References 1