GHSA-f67m-9j94-qv9j json
Parser creates invalid uninitialized value
published 4y ago modified 2mo ago also RUSTSEC-2022-0022
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is GHSA-f67m-9j94-qv9j in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | hyper | <0.14.12 >=0.0.0-0, <0.14.12 |
0.14.12 |
References
-
github.com
/hyperium/hyper/pull/2545
web
-
github.com
/hyperium/hyper
package
-
rustsec.org
/advisories/RUSTSEC-2022-0022.html
web, advisory
-
crates.io
/crates/hyper
package
Sources
- GitHub Advisory GHSA-f67m-9j94-qv9j
- OSV RUSTSEC-2022-0022
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.