rustsec-2020-0019
Vulnerability from osv_rustsec
Published
2020-05-19 12:00
Modified
2023-06-13 13:10
Summary
tokio-rustls reads may cause excessive memory usage
Details
tokio-rustls does not call process_new_packets immediately after read,
so the expected termination condition wants_read always returns true.
As long as new incoming data arrives faster than it is processed
and the reader does not return pending, data will be buffered.
This may cause DoS.
{
"affected": [
{
"database_specific": {
"categories": [
"denial-of-service"
],
"cvss": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "tokio-rustls",
"purl": "pkg:cargo/tokio-rustls"
},
"ranges": [
{
"events": [
{
"introduced": "0.12.0"
},
{
"fixed": "0.12.3"
},
{
"introduced": "0.13.0"
},
{
"fixed": "0.13.1"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2020-35875",
"GHSA-2jfv-g3fh-xq3v"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "`tokio-rustls` does not call `process_new_packets` immediately after `read`,\nso the expected termination condition `wants_read` always returns true.\nAs long as new incoming data arrives faster than it is processed\nand the reader does not return pending, data will be buffered.\n\nThis may cause DoS.",
"id": "RUSTSEC-2020-0019",
"modified": "2023-06-13T13:10:24Z",
"published": "2020-05-19T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/tokio-rustls"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2020-0019.html"
},
{
"type": "WEB",
"url": "https://github.com/tokio-rs/tls/pull/14"
}
],
"related": [],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "tokio-rustls reads may cause excessive memory usage"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…