# DRUPAL-CONTRIB-2023-045: This module enables users to log in by email address with minimal configurations.

> The module fails to implement flood control, allowing attackers to perform brute force attacks against user accounts.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Sep 2023

## What is DRUPAL-CONTRIB-2023-045?

DRUPAL-CONTRIB-2023-045 is a vulnerability in drupal/mail_login, published on 13 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This module enables users to log in by email address with minimal configurations.

Drupal core contains protection against brute force attacks via a flood control mechanism. This module's functionality did not replicate the flood control, enabling brute force attacks.

## Which versions are affected by DRUPAL-CONTRIB-2023-045?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/mail_login` | Packagist:https://packages.drupal.org/8 | All versions | 2.8.0 |

## How do I fix DRUPAL-CONTRIB-2023-045?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2023-045 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2023-045 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2023-045 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2023-045 is a vulnerability in drupal/mail_login, published on 13 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2023-045 in the wild and no public exploit code.

Affected product: drupal/mail_login. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-045/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-045/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2023-045

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2023-045/
Summaries are generated and may contain mistakes; the official description above is the record.