Question 1

Is there a bug in socket2 0.0.0-0?

Accepted Answer

`socket2` invalidly assumes the memory layout of std::net::SocketAddr The [`socket2`](https://crates.io/crates/socket2) 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. Fixed in socket2 0.3.16.

Question 2

Is there a bug in socket2?

Accepted Answer

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 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.
 Fixed in socket2 0.3.16.

Severity	Affected	Fixed in	Title	Status	Source
medium	0.0.0-0	0.3.16	`socket2` invalidly assumes the memory layout of std::net::SocketAddr The [`socket2`](https://crates.io/crates/socket2) 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.	fixed	osv:RUSTSEC-2020-0079
medium	any	0.3.16	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 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.	fixed	osv:GHSA-458v-4hrf-g3m4

socket2 known bugs