Most recent entries from all

cnvd-2021-13650

EUVD-2026-25234

fkie_cve-2021-26955

An issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because xcb::xproto::GetAtomNameReply::name() calls std::str::from_utf8_unchecked() on unvalidated bytes from an X server.

GHSA-3288-cwgw-ch86 — Unchecked Return Value in xcb

Affected: crates.io: xcb

gsd-2021-26955

RUSTSEC-2021-0019 — Multiple soundness issues

Affected: crates.io: xcb

## Calls `std::str::from_utf8_unchecked()` without any checks

The function `xcb::xproto::GetAtomNameReply::name()` calls `std::str::from_utf8_unchecked()` on the raw bytes that were received from the X11 server without any validity checks. The X11 server only prevents interior null bytes, but otherwise allows any X11 client to create an atom for arbitrary bytes.

This issue is tracked here: https://github.com/rust-x-bindings/rust-xcb/issues/96

## `xcb::xproto::GetPropertyReply::value()` allows arbitrary return types

The function `xcb::xproto::GetPropertyReply::value()` returns a slice of type `T` where `T` is an unconstrained type parameter. The raw bytes received from the X11 server are interpreted as the requested type.

The users of the `xcb` crate are advised to only call this function with the intended types. These are `u8`, `u16`, and `u32`.

This issue is tracked here: https://github.com/rust-x-bindings/rust-xcb/issues/95

## Out of bounds read in `xcb::xproto::change_property()`

`xcb::xproto::change_property` has (among others) the arguments `format: u8` and `data: &[T]`. The intended use is one of the following cases: - `format = 8` and `T = u8` - `format = 16` and `T = u16` - `format = 32` and `T = u32` However, this constraint is not enforced. For example, it is possible to call the function with `format = 32` and `T = u8`. In this case, a read beyond the end of the `data` slice is performed and the bytes are sent to the X11 server.

The users of the `xcb` cra…

UBUNTU-CVE-2021-26955

Affected: Ubuntu:22.04:LTS: rust-xcb