xcb
Rust bindings and wrapper for XCB.
View on Github
Activity
- Latest release
- 1mo ago
- Total releases
- 38
- Cadence
- ~34 days
- Last 12 months
- 2
Reach
- Stars
- 168
Details
- License
- MIT
- First release
- Feb 03, 2016
| Version | Released | |
|---|---|---|
1.7.1
patch
|
1.7.1
patch
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
1.7.0
unknown
|
1.7.0
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
1.6.0
unknown
|
1.6.0
unknown
Dependencies (8)
Changelog
Compare changes
|
|
1.5.0
unknown
1 CVE
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev |
1.5.0
unknown
Dependencies (8)
Changelog
Compare changes
|
|
1.4.0
unknown
1 CVE
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev |
1.4.0
unknown
Dependencies (8)
Changelog
Compare changes
|
|
1.3.0
unknown
1 CVE
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev |
1.3.0
unknown
Dependencies (8)
Changelog
Compare changes
|
|
1.2.2
unknown
1 CVE
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev |
1.2.2
unknown
Dependencies (8)
Changelog
Compare changes
|
|
1.2.1
unknown
1 CVE
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev |
1.2.1
unknown
Dependencies (8)
Changelog
Compare changes
|
|
1.2.0
unknown
1 CVE
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev | ||
1.1.1
unknown
1 CVE
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev | ||
1.1.0
unknown
1 CVE
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev | ||
1.0.0
unknown
1 CVE
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev | ||
1.0.0-beta.4
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
1.0.0-beta.3
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
1.0.0-beta.2
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
1.0.0-beta.1
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
1.0.0-beta.0
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.10.1
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.10.0
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.7.8
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.9.0
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.8.2
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.8.1
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.7.7
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.8.0
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.7.6
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.7.5
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.7.4
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.7.3
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.7.2
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.7.1
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.7.0
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.6.2
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.6.1
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.6.0
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.5.0
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.4.1
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.4.0
unknown
3 CVEs
GHSA-655h-hg88-5qmf
RUSTSEC-2025-0051
Aug 22, 2025
Rust XCB `xcb::Connection::connect_to_fd*` functions violate I/O safety
Low
Network
Low
None
None
The API of Starting in version 1.6.0, Fixed in
1.6.0
References
Updated Oct 28, 2025 · Source: OSV.dev
CVE-2021-26955
GHSA-mp6r-fgw2-rxfx
CVE-2021-26956
CVE-2021-26957
CVE-2021-26958
GHSA-2xpg-3hx4-fm9r
GHSA-3288-cwgw-ch86
GHSA-3cj3-jrrp-9rxf
RUSTSEC-2021-0019
Aug 25, 2021
Arbitrary return types in xcb
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
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 Fixed in
1.0.0
References Updated Mar 15, 2024 · Source: OSV.dev
CVE-2020-36205
GHSA-c8hq-x4mm-p6q6
RUSTSEC-2020-0097
Aug 25, 2021
Memory handling issues in xcb
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur. Fixed in
1.0.0
References Updated Nov 08, 2023 · Source: OSV.dev |