# CVE-2024-24983: Security feature bypass in Intel(R) Ethernet Network Controllers and Adapters E810 Series

> An unauthenticated attacker can cause a denial of service on Intel E810 Ethernet controllers by bypassing protection mechanisms.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2024
- **Updated:** 14 Aug 2024
- **Also known as:** GHSA-c6fj-cjw5-qrhj

## What is CVE-2024-24983?

CVE-2024-24983 is a high-severity vulnerability in Intel(R) Ethernet Network Controllers and Adapters E810 Series, published on 14 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Protection mechanism failure in firmware for some Intel(R) Ethernet Network Controllers and Adapters E810 Series before version 4.4 may allow an unauthenticated user to potentially enable denial of service via network access.

Weakness: CWE-693 (Protection Mechanism Failure)

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


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

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

## Is CVE-2024-24983 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-24983 is a high-severity vulnerability in Intel(R) Ethernet Network Controllers and Adapters E810 Series, published on 14 Aug 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-24983 in the wild and no public exploit code.

Affected product: Intel(R) Ethernet Network Controllers and Adapters E810 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-24983/ (Markdown: https://insights.sbomify.com/CVE-2024-24983/index.md)
```

## Sources

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

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