# CVE-2024-36454: Denial of service in IPCOM EX2 Series (V01L0x Series)

> Attackers can cause system reboot or suspension on IPCOM EX2 and VE2 series devices by sending specially crafted packets.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-v58c-6x2p-85gg

## What is CVE-2024-36454?

CVE-2024-36454 is a medium-severity denial of service vulnerability in Fsas Technologies Inc. IPCOM EX2 Series (V01L0x Series), published on 12 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of uninitialized resource issue exists in IPCOM EX2 Series (V01L0x Series) V01L07NF0201 and earlier, and IPCOM VE2 Series V01L07NF0201 and earlier. If this vulnerability is exploited, the system may be rebooted or suspended by receiving a specially crafted packet.

Weakness: CWE-908 (Use of Uninitialized Resource)

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


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

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

## Is CVE-2024-36454 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36454 is a medium-severity denial of service vulnerability in Fsas Technologies Inc. IPCOM EX2 Series (V01L0x Series), published on 12 Jun 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-36454 in the wild and no public exploit code.

Affected product: Fsas Technologies Inc. IPCOM EX2 Series (V01L0x Series). 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-36454/ (Markdown: https://insights.sbomify.com/CVE-2024-36454/index.md)
```

## Sources

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

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