# GHSA-f67m-9j94-qv9j: Parser creates invalid uninitialized value

> An attacker can trigger memory corruption in the HTTP parser by sending crafted requests, potentially leading to code execution or crashes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 May 2022
- **Also known as:** RUSTSEC-2022-0022

## What is GHSA-f67m-9j94-qv9j?

GHSA-f67m-9j94-qv9j is a memory corruption vulnerability in hyper, published on 10 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected versions of this crate called `mem::uninitialized()` in the HTTP1 parser to create values of type `httparse::Header` (from the `httparse` crate).
This is unsound, since `Header` contains references and thus must be non-null.
 
The flaw was corrected by avoiding the use of `mem::uninitialized()`, using `MaybeUninit` instead.

## Which versions are affected by GHSA-f67m-9j94-qv9j?

3 open source packages ship an affected version, including hyper.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hyper` | crates.io | All versions | 0.14.12 |
| `hyper` | crates.io | All versions | 0.14.12 |
| `hyper` | crates.io | From 0.0.0-0 | 0.14.12 |

## How do I fix GHSA-f67m-9j94-qv9j?

Upgrade hyper to 0.14.12 or later.

## Is GHSA-f67m-9j94-qv9j being exploited?

There is no known exploitation of GHSA-f67m-9j94-qv9j in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-f67m-9j94-qv9j and fix it if it is affected.

What it is: GHSA-f67m-9j94-qv9j is a memory corruption vulnerability in hyper, published on 10 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-f67m-9j94-qv9j in the wild and no public exploit code.

Affected packages and fixed versions:
- hyper (crates.io): affected all versions; fixed in 0.14.12
- hyper (crates.io): affected all versions; fixed in 0.14.12
- hyper (crates.io): affected from 0.0.0-0; fixed in 0.14.12

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/GHSA-f67m-9j94-qv9j/ (Markdown: https://insights.sbomify.com/GHSA-f67m-9j94-qv9j/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-f67m-9j94-qv9j

---
From sbomify Insights: https://insights.sbomify.com/GHSA-f67m-9j94-qv9j/
Summaries are generated and may contain mistakes; the official description above is the record.