Conrad Lara

The module fails to sufficiently isolate upload context between separate object operations within the same request. This can lead to objects being uploaded with incorrect access control list (ACL) entries or data corruption due to incorrect operation metadata. Exploitation requires the ability to trigger multiple file operations on S3FS.

Improper neutralization of input during web page generation allows for Cross-Site Scripting (XSS), a condition where malicious scripts are injected into trusted websites. The issue occurs because the autocomplete widget does not sufficiently escape user input. This cannot occur in a default installation and requires the presence of additional modules or custom code.

Improper neutralization of input during web page generation allows for Cross-Site Scripting (XSS). The Address Suggestion module, which provides address autocomplete functionality via configured providers, fails to sufficiently sanitize the data returned by these providers. Exploitation requires an attacker to inject malicious content into the data returned by a configured address provider and a user to perform a search that triggers the malicious suggestion.

A security issue exists in the Drupal Screenshot project. The project is currently marked as unsupported, and the security flaw remains unaddressed by the maintainer.

A security issue exists in the Drupal Screenshot project. The project is currently marked as unsupported, and the security flaw remains unaddressed by the maintainer.

An access bypass issue allows users possessing the administer users permission to view or generate recovery codes for other users.

Name of the Vulnerable Software and Affected Versions: Drupal Two-factor Authentication (TFA) versions 0.0.0 through 1.10.0 Description: The issue affects the two-factor authentication (TFA) mechanism, allowing exploitation of incorrectly configured access control security levels due to a privilege defined with unsafe actions. Recommendations: For versions 0.0.0 through 1.10.0, update to version 1.11.0 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Enterprise MFA - TFA for Drupal versions 0.0.0 through 4.8.0 Enterprise MFA - TFA for Drupal versions 5.2.0 through 5.2.0 Enterprise MFA - TFA for Drupal versions 0.0.0 through 5.0.* Enterprise MFA - TFA for Drupal versions 0.0.0 through 5.1.* Description: The issue affects the Enterprise MFA - TFA for Drupal module, allowing authentication bypass using an alternate path or channel. This is due to the module not sufficiently ensuring that known authorization routes are protected. Recommendations: For versions 0.0.0 through 4.8.0, update to version 4.8.0 or later. For version 5.2.0, update to version 5.2.1 or later. For versions 0.0.0 through 5.0.*, update to version 5.0.* or later. For versions 0.0.0 through 5.1.*, update to version 5.1.* or later. As a temporary workaround, consider restricting access to known authorization routes to minimize the risk of exploitation.

The issue is related to an Authentication Bypass by Capture-replay vulnerability in Drupal One Time Password, allowing remote services with stolen credentials.

The issue is related to an Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal One Time Password, allowing functionality bypass.

The issue is related to an Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal One Time Password, allowing functionality bypass.

Name of the Vulnerable Software and Affected Versions: Enterprise MFA - TFA for Drupal versions 0.0.0 through 4.6.x Enterprise MFA - TFA for Drupal versions 5.0.0 through 5.1.x Description: The issue is related to an Authentication Bypass Using an Alternate Path or Channel vulnerability in Enterprise MFA - TFA for Drupal, allowing authentication bypass. Recommendations: For Enterprise MFA - TFA for Drupal versions 0.0.0 through 4.6.x, update to version 4.7.0 or later. For Enterprise MFA - TFA for Drupal versions 5.0.0 through 5.1.x, update to version 5.2.0 or later.

Name of the Vulnerable Software and Affected Versions: Enterprise MFA - TFA for Drupal versions 0.0.0 through 4.6.x Enterprise MFA - TFA for Drupal versions 5.0.0 through 5.1.x Description: The issue is related to an Authentication Bypass Using an Alternate Path or Channel vulnerability in Enterprise MFA - TFA for Drupal, allowing authentication bypass. Recommendations: For Enterprise MFA - TFA for Drupal versions 0.0.0 through 4.6.x, update to version 4.7.0 or later. For Enterprise MFA - TFA for Drupal versions 5.0.0 through 5.1.x, update to version 5.2.0 or later.

Name of the Vulnerable Software and Affected Versions: Enterprise MFA - TFA for Drupal versions 0.0.0 through 4.6.x Enterprise MFA - TFA for Drupal versions 5.0.0 through 5.1.x Description: The issue is related to an Authentication Bypass by Capture-replay vulnerability in Enterprise MFA - TFA for Drupal. This allows remote services to be accessed with stolen credentials. Recommendations: For Enterprise MFA - TFA for Drupal versions 0.0.0 through 4.6.x, update to version 4.7.0 or later. For Enterprise MFA - TFA for Drupal versions 5.0.0 through 5.1.x, update to version 5.2.0 or later.

The issue is related to an Incorrect Authorization vulnerability in the Drupal Two-factor Authentication (TFA) module, allowing Forceful Browsing.

Name of the Vulnerable Software and Affected Versions: Intel SGX (affected versions not specified) Description: The issue is a side-channel timing attack against Intel SGX enclaves, which can lead to the complete compromise of Trusted Execution Environment (TEE) attestation. A proof of concept (PoC) has demonstrated key extraction in less than 4 seconds. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

The issue is related to incorrect session management in the Two-factor Authentication (TFA) module of the Drupal CMS system. This can allow a remote attacker to hijack a user's session. The problem affects the Two-factor Authentication (TFA) module, allowing session fixation.

The issue is related to a weak authentication vulnerability in the Two-factor Authentication (TFA) module for Drupal, which can be exploited to abuse authentication. This vulnerability is associated with weaknesses in the authentication procedure, allowing a remote attacker to bypass security restrictions.

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 issue. This is mitigated by the fact that it only applies when the site sets `$config['image.settings']['allow insecure derivatives']` or `$conf['image allow insecure derivatives']` to TRUE. The recommended and default setting is FALSE.