![]() ![]() Some sites may require configuration changes following this security release. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI. This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) $config or (Drupal 7) $conf to TRUE. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability. Access to a non-public file is checked only if it is stored in the "private" file system. ![]() 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. Under certain circumstances, this could lead to cross-site scripting, leaked cookies, or other vulnerabilities. The Media oEmbed iframe route does not properly validate the iframe domain setting, which allows embeds to be displayed in the context of the primary domain. 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. htaccess files and possible remote code execution on Apache web servers. ![]() This could allow bypassing the protections provided by Drupal core's default. 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. However, the protections for these two vulnerabilities previously did not work correctly together. Published: Ap11:15:08 AM -0400ĭrupal 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, forms added through contributed or custom modules or themes may be affected. No forms provided by Drupal core are known to be vulnerable. This may lead to a user being able to alter data they should not have access to. Under certain circumstances, the Drupal core form API evaluates form element access incorrectly. Review the release notes for your Drupal version if you have issues accessing private files after updating. This may result in users gaining access to private files that they should not have access to. The file download facility doesn't sufficiently sanitize file paths in certain situations. The associated identifier of this vulnerability is VDB-227755. It is recommended to upgrade the affected component. Upgrading to version 7.x-1.7 is able to address this issue. The manipulation leads to cross site scripting. Affected by this vulnerability is the function responsive_menus_admin_form_submit of the file responsive_menus.module of the component Configuration Setting Handler. A vulnerability classified as problematic was found in Responsive Menus 7.x-1.x-dev on Drupal. ![]()
0 Comments
Leave a Reply. |