![]() However, this API was not completely integrated with existing permissions, resulting in some possible access bypass for users who have access to use revisions of content generally, but who do not have access to individual items of node and media content. 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.ĭrupal 9.3 implemented a generic entity access API for entity revisions. 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. The associated identifier of this vulnerability is VDB-227755.ĭ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). 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. |