Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Correct affected version range on RUSTSEC-2019-003[34] to patched at 0.1.20 #221

Merged
merged 1 commit into from Jan 9, 2020
Merged

Correct affected version range on RUSTSEC-2019-003[34] to patched at 0.1.20 #221

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 3 additions & 3 deletions crates/http/RUSTSEC-2019-0033.toml
View file
Open in desktop
Expand Up @@ -13,12 +13,12 @@ the library will invoke `self.grow(0)` and start infinite probing.
This allows an attacker who controls the argument to `reserve()`
to cause a potential denial of service (DoS).
The flaw was corrected in 0.2.0 release of `http` crate.
The flaw was corrected in 0.1.20 release of `http` crate.
"""
patched_versions = [">= 0.2.0"]
patched_versions = [">= 0.1.20"]
url = "https://github.com/hyperium/http/issues/352"
categories = ["denial-of-service"]
keywords = ["http", "integer-overflow", "DoS"]

[affected.functions]
"http::header::HeaderMap::reserve" = ["< 0.2.0"]
"http::header::HeaderMap::reserve" = ["< 0.1.20"]
6 changes: 3 additions & 3 deletions crates/http/RUSTSEC-2019-0034.toml
View file
Open in desktop
Expand Up @@ -10,11 +10,11 @@ which introduced unsoundness in its public safe API.
[Failing to drop the Drain struct causes double-free](https://github.com/hyperium/http/issues/354),
and [it is possible to violate Rust's alias rule and cause data race with Drain's Iterator implementation](https://github.com/hyperium/http/issues/355).
The flaw was corrected in 0.2.0 release of `http` crate.
The flaw was corrected in 0.1.20 release of `http` crate.
"""
patched_versions = [">= 0.2.0"]
patched_versions = [">= 0.1.20"]
categories = ["memory-corruption"]
keywords = ["memory-safety", "double-free", "unsound"]

[affected.functions]
"http::header::HeaderMap::drain" = ["< 0.2.0"]
"http::header::HeaderMap::drain" = ["< 0.1.20"]