drupal/core
Affected
- introduced
8.0.0, fixed9.3.19(ecosystem) - introduced
9.4.0, fixed9.4.3(ecosystem)
Fixed versions
9.3.19, 9.4.3
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-drupal-2022-25277, CVE-2022-25277, GHSA-6955-67hm-vjjq
The record has no summary.
*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.
Not rated by the source.
8.0.0, fixed 9.3.19 (ecosystem)9.4.0, fixed 9.4.3 (ecosystem)9.3.19, 9.4.3
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: Drupal Advisory Database · MIT