# CVE-2024-9199: Rate limit vulnerability in Clibo Manager

> An attacker can bypass rate limits to send excessive emails, causing a denial of service in Clibo Manager.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2024
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-w36c-m53m-r93m

## What is CVE-2024-9199?

CVE-2024-9199 is a medium-severity denial of service vulnerability in Clibo Manager, published on 26 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rate limit vulnerability in Clibo Manager v1.1.9.2 that could allow an attacker to send a large number of emails to the victim in a short time, affecting availability and leading to a denial of service (DoS).

Weakness: CWE-799 (Improper Control of Interaction Frequency)

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

It affects 1 product.


Products: Clibomanager Clibo Manager.

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

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

## Is CVE-2024-9199 being exploited?

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

## Other vulnerabilities in Clibo Manager

- [CVE-2024-9198](https://insights.sbomify.com/CVE-2024-9198/): Stored Cross-Site Scripting vulnerability in Clibo Manager (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9199 is a medium-severity denial of service vulnerability in Clibo Manager, published on 26 Sep 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-9199 in the wild and no public exploit code.

Affected product: Clibo Manager. 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-9199/ (Markdown: https://insights.sbomify.com/CVE-2024-9199/index.md)
```

## Sources

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

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