CVE-2023-22466 Vulnerability Analysis & Exploit Details

CVE-2023-22466
Vulnerability Scoring

5.4
/10
Significant Risk

Security assessments indicate that CVE-2023-22466 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-22466 Details

Status: Modified

Last updated: 🕢 21 Nov 2024, 07:44 UTC
Originally published on: 🕙 04 Jan 2023, 22:15 UTC

Time between publication and last update: 686 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

CVE-2023-22466 Vulnerability Summary

CVE-2023-22466: 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`.

Assessing the Risk of CVE-2023-22466

Access Complexity Graph

The exploitability of CVE-2023-22466 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2023-22466

CVE-2023-22466 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2023-22466, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2023-22466, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2023-22466 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2023-22466 poses no threat to data integrity.
  • Availability: Low
    CVE-2023-22466 may slightly degrade system performance without fully affecting service availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.122% (probability of exploit)

EPSS Percentile: 48.14% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 51.86% of others.

CVE-2023-22466 References

External References

CWE Common Weakness Enumeration

CWE-665

CAPEC Common Attack Pattern Enumeration and Classification

  • Leveraging Race Conditions CAPEC-26 The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions CAPEC-29 This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.

Vulnerable Configurations

  • cpe:2.3:a:tokio:tokio:1.7.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.7.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.7.1:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.7.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.7.2:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.7.2:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.7.3:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.7.3:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.8.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.8.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.8.1:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.8.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.8.2:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.8.2:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.8.3:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.8.3:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.8.4:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.8.4:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.8.5:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.8.5:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.9.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.9.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.10.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.10.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.10.1:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.10.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.11.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.11.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.12.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.12.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.13.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.13.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.13.1:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.13.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.14.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.14.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.14.1:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.14.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.15.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.15.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.16.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.16.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.16.1:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.16.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.17.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.17.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.18.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.18.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.18.1:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.18.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.18.2:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.18.2:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.18.3:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.18.3:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.19.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.19.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.19.1:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.19.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.19.2:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.19.2:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.20.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.20.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.20.1:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.20.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.20.2:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.20.2:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.21.0:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.21.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.21.1:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.21.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:tokio:tokio:1.21.2:*:*:*:*:rust:*:*
    cpe:2.3:a:tokio:tokio:1.21.2:*:*:*:*:rust:*:*

Protect Your Infrastructure against CVE-2023-22466: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...