# CVE-2023-51391: Micrium OS Network uC-HTTP server header parsing invalid pointer dereference vulnerability

> An attacker can crash an IoT device by sending malformed HTTP headers to the Micrium OS Network HTTP Server, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-j435-3f42-ww7p

## What is CVE-2023-51391?

CVE-2023-51391 is a high-severity vulnerability, published on 16 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A bug in Micrium OS Network HTTP Server permits an invalid pointer dereference during header processing - potentially allowing a device crash and Denial of Service.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2023-51391?


## How do I fix CVE-2023-51391?

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

## Is CVE-2023-51391 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51391 and fix it if it is affected.

What it is: CVE-2023-51391 is a high-severity vulnerability, published on 16 Apr 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-2023-51391 in the wild and no public exploit code.

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-2023-51391/ (Markdown: https://insights.sbomify.com/CVE-2023-51391/index.md)
```

## Sources

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

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