# CVE-2024-35246: Westermo L210-F2G Lynx Improper Control of Interaction Frequency

> An attacker can cause a denial-of-service condition on Westermo L210-F2G Lynx switches by sending repeated packets.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-rqr4-mc25-2cvq

## What is CVE-2024-35246?

CVE-2024-35246 is a high-severity denial of service vulnerability in Westermo L210-F2G Lynx, published on 20 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker may be able to cause a denial-of-service condition by sending many packets repeatedly.

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

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

It affects 1 product.


Products: Westermo L210-F2g Lynx Firmware.

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

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

## Is CVE-2024-35246 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35246 is a high-severity denial of service vulnerability in Westermo L210-F2G Lynx, published on 20 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-35246 in the wild and no public exploit code.

Affected product: Westermo L210-F2G Lynx. 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-35246/ (Markdown: https://insights.sbomify.com/CVE-2024-35246/index.md)
```

## Sources

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

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