CVE-2022-25275: High severity drupal vulnerability

Published Jul 20, 2022
·
Updated

Drupal core - Moderately critical - Information Disclosure - SA-CORE-2022-012

Other sources

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']['allowinsecurederivatives'] or (Drupal 7) $conf['imageallowinsecurederivatives'] 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.

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']['allowinsecurederivatives'] or (Drupal 7) $conf['imageallowinsecurederivatives'] 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.

Affected Software

7 affected componentsFixes available
composer/drupal/core>=7.0.0, <7.91.0, >=8.9.0, <8.10.0, >=9.0.0, <9.1.0, >=9.1.0, <9.2.0, >=9.2.0, <9.3.0, >=9.3.0, <9.3.19, >=9.4.0, <9.4.3
composer/drupal/core>=9.4.0<9.4.3
9.4.3
composer/drupal/core>=8.0.0<9.3.19
9.3.19
composer/drupal/core>=7.0.0<7.91
7.91
Drupal Drupal>=7.0<7.91
Drupal Drupal>=8.0.0<9.3.19
Drupal Drupal>=9.4.0<9.4.3

Event History

Jul 20, 2022
Advisory Published
06:00 PM
Apr 26, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the vulnerability ID for this Drupal vulnerability?

The vulnerability ID for this Drupal vulnerability is CVE-2022-25275.

2

What is the severity level of CVE-2022-25275?

The severity level of CVE-2022-25275 is moderately critical.

3

What is the type of vulnerability associated with CVE-2022-25275?

CVE-2022-25275 is an information disclosure vulnerability.

4

Which software versions are affected by CVE-2022-25275?

Versions 7.0.0 to 7.91.0, 8.9.0 to 8.10.0, 9.0.0 to 9.1.0, 9.1.0 to 9.2.0, 9.2.0 to 9.3.0, and 9.3.0 to 9.3.19 of Drupal core are affected by CVE-2022-25275.

5

How can I fix CVE-2022-25275?

To fix CVE-2022-25275, it is recommended to update to the latest available version of Drupal core.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203