Approved changes feed: RSS · Atom
cpe:2.3:a:tokio-rs:tokio:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Tokio Rs (f66f7134-7f98-5eb5-8851-4ebd75b4ec87) |
|---|---|
| Product | Tokio (27c2bbda-66d0-5299-81c6-d963271ea90e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-22466 |
vulnerable | 2026-06-08 05:54:26.380616 |
Tokio's reject_remote_clients configuration may get dropped when creating a Windows named pipe
MEDIUM (5.4)
Tokio is a runtime for writing applications with Rust. Starting with version 1.7.0 and prior to versions 1.18.4, 1.20.3, and 1.23.1, when configuring a Windows named pipe server, setting `pipe_mode` will reset `reject_remote_clients` to `false`. If the application has previously configured `reject_remote_clients` to `true`, this effectively undoes the configuration. Remote clients may only access the named pipe if the named pipe's associated path is accessible via a publicly shared folder (SMB). Versions 1.23.1, 1.20.3, and 1.18.4 have been patched. The fix will also be present in all releases starting from version 1.24.0. Named pipes were introduced to Tokio in version 1.7.0, so releases older than 1.7.0 are not affected. As a workaround, ensure that `pipe_mode` is set first after initializing a `ServerOptions`.
Published: 2023-01-04T21:47:09.400Z
Updated: 2025-03-10T21:32:32.950Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.