Jakob P

An incorrect authorization issue allows forceful browsing. The module fails to sufficiently restrict access to fields configured as Private on entity types that lack an author field (such as a user account or owner). Consequently, these Private fields can be viewed, and if the entity is editable, it can be modified by any user who can view it, including anonymous users. This issue does not affect fields set to Private on nodes, users, media, comments, or other entity types with an author, nor does it affect fields using Custom permissions.

Incorrect authorization allows forceful browsing due to insufficient verification of administrative privileges when checking access to protected fields. This allows users assigned a role with the machine name `administrator` (provided it is not flagged as the site's actual administrator role) to bypass field-level access restrictions and gain unauthorized view and edit access to protected fields.

An authentication bypass issue exists where the module fails to fully invalidate a solved CAPTCHA session. This allows a protected form that has been submitted once to be submitted again without solving a new challenge. This flaw weakens protection against automated submissions, including login brute-forcing, comment spam, and spam registrations.

Incorrect authorization allows forceful browsing. The module enables site builders to control entity page views by showing the page, returning access denied or not found responses, or redirecting visitors. One issue allows anonymous visitors to bypass these behaviors using a specific query parameter, potentially viewing content intended to be hidden or avoiding redirects. Additionally, per-entity settings are stored in fields that lack proper access control; while the module checks permissions to display settings on the edit form, the fields themselves follow default access. This allows users with entity edit permissions to modify these settings if a write path that bypasses the entity form is available, such as REST, JSON:API with writes enabled, or Views Bulk Operations.

Drupal Shield fails to sufficiently limit the number of authentication attempts when an anonymous visitor repeatedly submits basic authentication credentials. This allows for brute force attacks against the HTTP basic authentication prompt used to protect non-public sites from being viewed, crawled, or indexed. The risk is reduced if long, randomly generated passwords are used.

The Automated Logout module for Drupal does not adequately protect its routes against Cross-Site Request Forgery (CSRF). This allows an attacker to trigger the logout route without the user’s knowledge or consent. The module is designed to allow site administrators to log users out after a period of inactivity.

A functionality bypass exists in Drupal CAPTCHA due to insufficient invalidation of security tokens. An attacker may bypass the CAPTCHA on subsequent submissions if they first successfully solve at least one CAPTCHA manually to obtain valid tokens.

A missing authorization issue exists in Drupal Acquia DAM, allowing for forceful browsing. This allows unauthorized access to resources.

Name of the Vulnerable Software and Affected Versions: Drupal Panels versions 0.0.0 through 4.9.0 Description: The issue affects Drupal Panels due to missing authentication for a critical function, allowing exploitation of incorrectly configured access control security levels. Recommendations: For versions 0.0.0 through 4.9.0, update to version 4.9.0 or later to resolve the issue.

A Cross-Site Request Forgery (CSRF) issue affects the Drupal Google Tag module, allowing unauthorized actions to be performed on behalf of a user. This issue can be exploited to perform actions without the user's knowledge or consent.

The issue is related to Improper Neutralization of Input During Web Page Generation, also known as Cross-site Scripting (XSS). This allows for Cross-Site Scripting (XSS) attacks.