DRUPAL-CORE-2022-014 in drupal/core
Published 20 Jul 2022 · Updated 19 Sept 2026
Affected package
- Affected
- >=8.0.0 <9.3.19 · >=9.4.0 <9.4.3
- Fixed in
- 9.3.19, 9.4.3
composer require drupal/core:^9.4.3Details
*Updated 2022-07-20 19:45 UTC to indicate that this only affects Apache web servers.*
Drupal core sanitizes filenames with dangerous extensions upon upload (reference: SA-CORE-2020-012) and strips leading and trailing dots from filenames to prevent uploading server configuration files (reference: SA-CORE-2019-010).
However, the protections for these two vulnerabilities previously did not work correctly together. As a result, if the site were configured to allow the upload of files with an htaccess extension, these files' filenames would not be properly sanitized. This could allow bypassing the protections provided by Drupal core's default .htaccess files and possible remote code execution on Apache web servers.
This issue is mitigated by the fact that it requires a field administrator to explicitly configure a file field to allow htaccess as an extension (a restricted permission), or a contributed module or custom code that overrides allowed file uploads.
Is DRUPAL-CORE-2022-014 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/core, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.