# CVE-2024-1104: Temporary denial of service during a brute force attack

> An unauthenticated attacker can bypass brute force protections to cause a temporary denial of service for all users of the Webserv2 service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 22 Feb 2024
- **Updated:** 14 Aug 2024
- **Also known as:** GHSA-w9jf-wgxm-ggqj

## What is CVE-2024-1104?

CVE-2024-1104 is a high-severity vulnerability in Areal Topkapi Webserv2, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote attacker can bypass the brute force prevention mechanism and disturb the webservice for all users.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2024-1104?

It affects 1 product.


Products: Areal-Topkapi Webserv2.

## How do I fix CVE-2024-1104?

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

## Is CVE-2024-1104 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1104 and fix it if it is affected.

What it is: CVE-2024-1104 is a high-severity vulnerability in Areal Topkapi Webserv2, published on 22 Feb 2024. 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-2024-1104 in the wild and no public exploit code.

Affected product: Areal Topkapi Webserv2. 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-2024-1104/ (Markdown: https://insights.sbomify.com/CVE-2024-1104/index.md)
```

## Sources

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

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