search

vipinsun / cactus

Hyperledger Cactus is a new approach to the blockchain interoperability problem
https://wiki.hyperledger.org/display/cactus
Apache License 2.0
0 stars 1 forks source link

CVE-2021-21299 (Medium) detected in hyper-0.13.9.crate, hyper-0.12.35.crate #20

Open mend-bolt-for-github[bot] opened 3 years ago

mend-bolt-for-github[bot] commented 3 years ago

CVE-2021-21299 - Medium Severity Vulnerability

Vulnerable Libraries - hyper-0.13.9.crate, hyper-0.12.35.crate

hyper-0.13.9.crate

A fast and correct HTTP library.

Library home page: https://crates.io/api/v1/crates/hyper/0.13.9/download

Path to dependency file: /packages/cactus-plugin-keychain-vault/src/cactus-keychain-vault-server/rust/gen/Cargo.toml

Path to vulnerable library: /packages/cactus-plugin-keychain-vault/src/cactus-keychain-vault-server/rust/gen/Cargo.toml

Dependency Hierarchy: - :x: **hyper-0.13.9.crate** (Vulnerable Library)

hyper-0.12.35.crate

A fast and correct HTTP library.

Library home page: https://crates.io/api/v1/crates/hyper/0.12.35/download

Path to dependency file: /packages/cactus-plugin-keychain-vault/src/cactus-keychain-vault-server/rust/gen/Cargo.toml

Path to vulnerable library: /packages/cactus-plugin-keychain-vault/src/cactus-keychain-vault-server/rust/gen/Cargo.toml

Dependency Hierarchy: - hashicorp_vault-1.1.0.crate (Root Library) - reqwest-0.9.24.crate - :x: **hyper-0.12.35.crate** (Vulnerable Library)

Found in HEAD commit: ceec9f73fd05cfdbf0061d53c9d0c42d43e85d22

Found in base branch: master

Vulnerability Details

hyper is an open-source HTTP library for Rust (crates.io). In hyper from version 0.12.0 and before versions 0.13.10 and 0.14.3 there is a vulnerability that can enable a request smuggling attack. The HTTP server code had a flaw that incorrectly understands some requests with multiple transfer-encoding headers to have a chunked payload, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that understands the request payload boundary differently can result in "request smuggling" or "desync attacks". To determine if vulnerable, all these things must be true: 1) Using hyper as an HTTP server (the client is not affected), 2) Using HTTP/1.1 (HTTP/2 does not use transfer-encoding), 3) Using a vulnerable HTTP proxy upstream to hyper. If an upstream proxy correctly rejects the illegal transfer-encoding headers, the desync attack cannot succeed. If there is no proxy upstream of hyper, hyper cannot start the desync attack, as the client will repair the headers before forwarding. This is fixed in versions 0.14.3 and 0.13.10. As a workaround one can take the following options: 1) Reject requests that contain a `transfer-encoding` header, 2) Ensure any upstream proxy handles `transfer-encoding` correctly.

Publish Date: 2021-02-11

URL: CVE-2021-21299

CVSS 3 Score Details (4.8)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://rustsec.org/advisories/RUSTSEC-2021-0020.html

Release Date: 2021-02-11

Fix Resolution: hyper - 0.13.10,0.14.3

Step up your Open Source Security Game with Mend here

mend-bolt-for-github[bot] commented 1 year ago

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

mend-bolt-for-github[bot] commented 1 year ago

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.