Affected forms are uncommon, but in certain cases an attacker could alter critical or sensitive data. This could allow an attacker to inject disallowed values or overwrite data. This vulnerability only affects sites using Drupal's revision system.ĭrupal core's form API has a vulnerability where certain contributed or custom modules' forms may be vulnerable to improper input validation. 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. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.ĭrupal 9.3 implemented a generic entity access API for entity revisions. 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.
#Drupal security kit code#
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. However, forms added through contributed or custom modules or themes may be affected.ĭ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). 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. This vulnerability is present in paid versions of the miniOrange Drupal SAML SP product affecting Drupal 7, 8, and 9. Xecurify recommends updating miniOrange modules to their most recent versions. This vulnerability is not mitigated by configuring the module to enforce signatures or certificate checks. An attacker with access to a HTTP-request intercepting method is able to bypass authentication and authorization by removing the SAML Assertion Signature - impersonating existing users and existing roles, including administrative users/roles. Xecurify's miniOrange Premium, Standard, and Enterprise Drupal SAML SP modules possess an authentication and authorization bypass vulnerability.
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.
#Drupal security kit download#
The file download facility doesn't sufficiently sanitize file paths in certain situations.
0 kommentar(er)
