# CVE-2024-46666: Denial of service in FortiOS

> Remote unauthenticated attackers can cause denial of service to the FortiOS GUI via crafted requests, requiring administrators to apply vendor patches.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2025
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-53h9-qp9v-954c

## What is CVE-2024-46666?

CVE-2024-46666 is a medium-severity denial of service vulnerability in Fortinet Fortios, published on 14 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An allocation of resources without limits or throttling [CWE-770] vulnerability in FortiOS versions 7.6.0, versions 7.4.4 through 7.4.0, 7.2 all versions, 7.0 all versions, 6.4 all versions may allow a remote unauthenticated attacker to prevent access to the GUI via specially crafted requests directed at specific endpoints.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Fortinet Fortios.

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

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

## Is CVE-2024-46666 being exploited?

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

## Other vulnerabilities in Fortinet Fortios

- [CVE-2024-23113](https://insights.sbomify.com/CVE-2024-23113/): Fortinet Multiple Products Format String (critical 9.8, exploited in the wild)
- [CVE-2022-40684](https://insights.sbomify.com/CVE-2022-40684/): Fortinet Multiple Products Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-55591](https://insights.sbomify.com/CVE-2024-55591/): Fortinet FortiOS and FortiProxy Authentication Bypass (critical 9.6, exploited in the wild)
- [CVE-2024-21762](https://insights.sbomify.com/CVE-2024-21762/): Fortinet FortiOS Out-of-Bound Write (critical 9.6, exploited in the wild)
- [CVE-2022-42475](https://insights.sbomify.com/CVE-2022-42475/): Fortinet FortiOS Heap-Based Buffer Overflow (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-46666 is a medium-severity denial of service vulnerability in Fortinet Fortios, published on 14 Jan 2025. 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-46666 in the wild and no public exploit code.

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

## Sources

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

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