Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
110 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
The Drupal project uses the PEAR ArchiveTar library. The PEAR ArchiveTar library has released a security update that impacts Drupal. For more information please see: CVE-2020-28948 CVE-2020-28949 Multiple vulnerabilities are possible if Drupal is configured to allow .tar, .tar.gz, .bz2, or .tlz file uploads and processes them. To mitigate this issue, prevent untrusted users from uploading .tar, .tar.gz, .bz2, or .tlz files.
Recommended action: Upgrade to 9.0.9, 8.9.10, 8.8.12 or 7.75 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Drupal 7 has an Open Redirect vulnerability. For example, a user could be tricked into visiting a specially crafted link which would redirect them to an arbitrary external URL. The vulnerability is caused by insufficient validation of the destination query parameter in the drupalgoto() function. Other versions of Drupal core are not vulnerable.
Recommended action: Upgrade to 7.70 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The Drupal project uses the third-party library CKEditor, which has released a security improvement that is needed to protect some Drupal configurations. Vulnerabilities are possible if Drupal is configured to use the WYSIWYG CKEditor for your site's users. An attacker that can create or edit content may be able to exploit this Cross Site Scripting (XSS) vulnerability to target users with access to the WYSIWYG CKEditor, and this may include site admins with privileged access. The latest versions of Drupal update CKEditor to 4.14 to mitigate the vulnerabilities.
Recommended action: Upgrade to 8.8.4 or 8.7.12 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The Drupal project uses the third-party library ArchiveTar, which has released a security improvement that is needed to protect some Drupal configurations. Multiple vulnerabilities are possible if Drupal is configured to allow .tar, .tar.gz, .bz2 or .tlz file uploads and processes them. The latest versions of Drupal update ArchiveTar to 1.4.9 to mitigate the file processing vulnerabilities.
Recommended action: Upgrade to 8.8.1, 8.7.11 or 7.69 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The Media Library module has a security vulnerability whereby it doesn't sufficiently restrict access to media items in certain configurations. Solution: If you are using Drupal 8.7.x, you should upgrade to Drupal 8.7.11. If you are using Drupal 8.8.x, you should upgrade to Drupal 8.8.1. Versions of Drupal 8 prior to 8.7.x are end-of-life and do not receive security coverage. Alternatively, you may mitigate this vulnerability by unchecking the "Enable advanced UI" checkbox on /admin/config/media/media-library. (This mitigation is not available in 8.7.x.)
Recommended action: Upgrade to 8.8.1 or 8.7.11 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Drupal 8 core's filesaveupload() function does not strip the leading and trailing dot ('.') from filenames, like Drupal 7 did. Users with the ability to upload files with any extension in conjunction with contributed modules may be able to use this to upload system files such as .htaccess in order to bypass protections afforded by Drupal's default .htaccess file. After this fix, filesaveupload() now trims leading and trailing dots from filenames.
Recommended action: Upgrade to 8.8.1 or 8.7.11 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A visit to install.php can cause cached data to become corrupted. This could cause a site to be impaired until caches are rebuilt.
Recommended action: Upgrade to 8.8.1 or 8.7.11 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The Contextual Links module doesn't sufficiently validate the requested contextual links. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "access contextual links".
Recommended action: Upgrade to 8.6.2 or 8.5.8 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In Drupal core, when sending email some variables were not being sanitized for shell arguments in DefaultMailSystem::mail(), which could lead to remote code execution.
Recommended action: Upgrade to 8.6.2, 8.5.8 or 7.60 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Drupal core and contributed modules frequently use a "destination" query string parameter in URLs to redirect users to a new destination after completing an action on the current page. Under certain circumstances, malicious users can use this parameter to construct a URL that will trick users into being redirected to a 3rd party website, thereby exposing the users to potential social engineering attacks.
Recommended action: Upgrade to 8.6.2 or 8.5.8 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The path module in Drupal allows users with the 'administer paths' to create pretty URLs for content. In certain circumstances the user can enter a particular path that triggers an open redirect to a malicious url.
Recommended action: Upgrade to 8.6.2, 8.5.8 or 7.60 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In some conditions, drupal content moderation fails to check a users access to use certain transitions, leading to an access bypass.
Recommended action: Upgrade to 8.6.2 or 8.5.8 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x. This potentially allows attackers to exploit multiple attack vectors on a Drupal site, which could result in the site being compromised. This vulnerability is related to Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-002. Both SA-CORE-2018-002 and this vulnerability are being exploited in the wild.
Recommended action: Upgrade to 8.5.3, 8.4.8 or 7.59 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The Comment module allows users to reply to comments. In certain cases, an attacker could make comment reply requests that would trigger a denial of service (DOS). Sites that do not use the Comment module are not affected.
Recommended action: Upgrade to 10.2.2 or 10.1.8 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In certain scenarios, Drupal's JSON:API module will output error backtraces. With some configurations, this may cause sensitive information to be cached and made available to anonymous users, leading to privilege escalation. This vulnerability only affects sites with the JSON:API module enabled, and can be mitigated by uninstalling JSON:API. The core REST and contributed GraphQL modules are not affected.
Recommended action: Upgrade to 10.1.4, 10.0.11 or 9.5.11 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The file download facility doesn't sufficiently sanitize file paths in certain situations. This may result in users gaining access to private files that they should not have access to. Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing private files after updating.
Recommended action: Upgrade to 10.0.8, 9.5.8, 9.4.14 or 7.96 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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. Under certain circumstances, this could lead to cross-site scripting, leaked cookies, or other vulnerabilities. Drupal 7 core does not include the Media module and therefore is not affected.
Recommended action: Upgrade to 9.4.3 or 9.3.19 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Drupal core's form API has a vulnerability where certain contributed or custom modules' forms may be vulnerable to improper input validation. This could allow an attacker to inject disallowed values or overwrite data. Affected forms are uncommon, but in certain cases an attacker could alter critical or sensitive data. Drupal 7 is not affected.
Recommended action: Upgrade to 9.3.12 or 9.2.18 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Drupal 9.3 implemented a generic entity access API for entity revisions. 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 vulnerability only affects sites using Drupal's revision system. All releases prior to Drupal 9.3 (including Drupal 7) are not affected.
Recommended action: Upgrade to 9.3.12 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Drupal core form API evaluates form element access incorrectly. This can lead to a user being able to alter data they should not have access to.
Recommended action: Upgrade to 9.4.3 or 9.3.19 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Drupal core sanitizes filenames with dangerous extensions upon upload and strips leading and trailing dots from filenames to prevent uploading server configuration files. 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.
Recommended action: Upgrade to 9.4.3 or 9.3.19 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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. Access to a non-public file is checked only if it is stored in the "private" file system. However, some contributed modules provide additional file systems, or schemes, which may lead to this vulnerability. This vulnerability is mitigated by the fact that it only applies when the site sets (Drupal 9) $config['image.settings']['allowinsecurederivatives'] or (Drupal 7) $conf['imageallowinsecurederivatives'] to TRUE. The recommended and default setting is FALSE, and Drupal core does not provide a way to change that in the admin UI. Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing files or image styles after updating.
Recommended action: Upgrade to 9.4.3, 9.3.19 or 7.91 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Cross-site scripting vulnerability in Drupal Core allows an attacker could leverage the way that HTML is rendered for affected forms in order to exploit the vulnerability. This issue affects: Drupal Core 8.8.X versions prior to 8.8.10; 8.9.X versions prior to 8.9.6; 9.0.X versions prior to 9.0.6.
Recommended action: Upgrade to 9.0.6, 8.9.6 or 8.8.10 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Cross Site Request Forgery vulnerability in Drupal Core Form API does not properly handle certain form input from cross-site requests, which can lead to other vulnerabilities.
Recommended action: Upgrade to 9.0.1, 8.9.1, 8.8.8 or 7.72 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Access bypass vulnerability in of Drupal Core Workspaces allows an attacker to access data without correct permissions. The Workspaces module doesn't sufficiently check access permissions when switching workspaces, leading to an access bypass vulnerability. An attacker might be able to see content before the site owner intends people to see the content. This vulnerability is mitigated by the fact that sites are only vulnerable if they have installed the experimental Workspaces module. This issue affects Drupal Core8.8.X versions prior to 8.8.10; 8.9.X versions prior to 8.9.6; 9.0.X versions prior to 9.0.6.
Recommended action: Upgrade to 9.0.6, 8.9.6 or 8.8.10 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.