# CVE-2013-2198: Auth bypass in Login Security

> Attackers can bypass intended restrictions in the Drupal Login Security module by using a crafted username.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-46hf-hf23-q64q

## What is CVE-2013-2198?

CVE-2013-2198 is a critical authentication bypass vulnerability in Login Security, published on 30 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Login Security module 6.x-1.x before 6.x-1.3 and 7.x-1.x before 7.x-1.3 for Drupal allows attackers to bypass intended restrictions via a crafted username.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2013-2198?

It affects 1 product.


Products: Login Security Project Login Security.

## How do I fix CVE-2013-2198?

No fix has been published for CVE-2013-2198 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-2198 being exploited?

There is no known exploitation of CVE-2013-2198 in the wild and no public exploit code.

## Other vulnerabilities in Login Security

- [CVE-2013-2197](https://insights.sbomify.com/CVE-2013-2197/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2198 and fix it if it is affected.

What it is: CVE-2013-2198 is a critical authentication bypass vulnerability in Login Security, published on 30 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2198 in the wild and no public exploit code.

Affected product: Login Security. 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/CVE-2013-2198/ (Markdown: https://insights.sbomify.com/CVE-2013-2198/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2198
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2198
- OSV: https://osv.dev/vulnerability/CVE-2013-2198

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-2198/
Summaries are generated and may contain mistakes; the official description above is the record.