mio invalidly assumes the memory layout of std::net::SocketAddr
The mio crate has assumed std::net::SocketAddrV4 and std::net::SocketAddrV6 have the same memory layout as the system C representation sockaddr. It has simply casted the pointers to convert the socket addresses to the system representation. The standard library does not say anything about the memory layout, and this will cause invalid memory access if the standard library changes the implementation. No warnings or errors will be emitted once the change happens.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-35922US | medium5.5 | — | ||
An issue was discovered in the mio crate before 0.7.6 for Rust. It has false expectations about the std::net::SocketAddr memory representation. | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/tokio-rs/mioPACKAGE
- https://github.com/tokio-rs/mio/commit/152e0751f0be1c9b0cbd6778645b76bcb0eba93cWEB
- https://github.com/tokio-rs/mio/issues/1386WEB
- https://github.com/tokio-rs/mio/pull/1388WEB
- https://nvd.nist.gov/vuln/detail/CVE-2020-35922ADVISORY
- https://rustsec.org/advisories/RUSTSEC-2020-0081.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan