Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Drupal | Drupal | >= 7.0, < 7.91 |
References
- https://www.drupal.org/sa-core-2022-012Vendor Advisory
- https://www.drupal.org/sa-core-2022-012Vendor Advisory
FAQ
What is CVE-2022-25275?
CVE-2022-25275 is a vulnerability with a CVSS score of 7.5 (HIGH). 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. A...
How severe is CVE-2022-25275?
CVE-2022-25275 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-25275?
Check the references section above for vendor advisories and patch information. Affected products include: Drupal Drupal.