GHSA-655h-hg88-5qmf
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Impact
The API of `xcb::Connection` has constructors which allow an arbitrary `RawFd` to be used as a socket connection. On either failure of these constructors or on the drop of `Connection`, it closes the associated file descriptor. Thus, a program which uses an `OwnedFd` (such as a `UnixStream`) as the file descriptor can close the file descriptor and continue to attempt using it or close an already-closed file descriptor, violating I/O safety. Starting in version 1.6.0, `xcb` provides `Connection::connect_with_fd` and `Connection::connect_with_fd_and_extensions` as safe alternatives and deprecates the problematic functions.
An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of data or systems being changed.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| rust | xcb | < 1.6.0 | 1.6.0 |
Weakness classification
References
- GitHub advisory
- https://github.com/advisories/GHSA-655h-hg88-5qmf
- https://github.com/rust-x-bindings/rust-xcb/issues/167
- https://github.com/rust-x-bindings/rust-xcb/issues/282
- https://github.com/rust-x-bindings/rust-xcb/pull/283
- https://github.com/rustsec/advisory-db/pull/2355
- https://github.com/rust-x-bindings/rust-xcb/commit/da830976870c1174e3b33eb0643177be3991c002
- https://rustsec.org/advisories/RUSTSEC-2025-0051.html