socket2
Affected
- introduced
0.0.0-0, fixed0.3.16(semver)
Fixed versions
0.3.16
Fix
- Fixed version
0.3.16cargo update -p socket2 --precise 0.3.16
Advisory
Also known as: CVE-2020-35919, CVE-2020-35920, GHSA-458v-4hrf-g3m4, GHSA-c79c-gwph-gqfm, RUSTSEC-2020-0078
socket2 invalidly assumes the memory layout of std::net::SocketAddr
The `socket2` crate has assumed std::net::SocketAddrV4
and std::net::SocketAddrV6 have the same memory layout as the system C representationsockaddr. 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.
Medium Basis: CVSS v3 score 5.5, vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
0.0.0-0, fixed 0.3.16 (semver)0.3.16
0.3.16cargo update -p socket2 --precise 0.3.16Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0