Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2022-23639

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Published: Feb 15, 2022 | Modified: Nov 21, 2024
CVSS 3.x
8.1
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2022-23639
CWEhttps://cwe.mitre.org/data/definitions/362.html

crossbeam-utils provides atomics, synchronization primitives, scoped threads, and other utilities for concurrent programming in Rust. crossbeam-utils prior to version 0.8.7 incorrectly assumed that the alignment of {i,u}64 was always the same as Atomic{I,U}64. However, the alignment of {i,u}64 on a 32-bit target can be smaller than Atomic{I,U}64. This can cause unaligned memory accesses and data race. Crates using fetch_* methods with AtomicCell<{i,u}64> are affected by this issue. 32-bit targets without Atomic{I,U}64 and 64-bit targets are not affected by this issue. This has been fixed in crossbeam-utils 0.8.7. There are currently no known workarounds.

Weakness

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Software

NameVendorStart VersionEnd Version
CrossbeamCrossbeam_project*0.8.7 (excluding)
CargoUbuntubionic*
CargoUbuntuesm-apps/xenial*
CargoUbuntuimpish*
CargoUbuntukinetic*
CargoUbuntutrusty*
CargoUbuntuxenial*
FirefoxUbuntubionic*
FirefoxUbuntudevel*
FirefoxUbuntufocal*
FirefoxUbuntuimpish*
FirefoxUbuntujammy*
FirefoxUbuntukinetic*
FirefoxUbuntulunar*
FirefoxUbuntumantic*
FirefoxUbuntunoble*
FirefoxUbuntuoracular*
FirefoxUbuntuplucky*
FirefoxUbuntuquesting*
FirefoxUbuntutrusty*
FirefoxUbuntuxenial*
LibrsvgUbuntutrusty*
LibrsvgUbuntuxenial*
Mozjs38Ubuntubionic*
Mozjs38Ubuntuesm-apps/bionic*
Mozjs38Ubuntuupstream*
Mozjs52Ubuntubionic*
Mozjs52Ubuntuesm-apps/focal*
Mozjs52Ubuntuesm-infra/bionic*
Mozjs52Ubuntufocal*
Mozjs52Ubuntuupstream*
Mozjs68Ubuntuesm-infra/focal*
Mozjs68Ubuntufocal*
Mozjs68Ubuntuupstream*
Mozjs78Ubuntuesm-apps/jammy*
Mozjs78Ubuntuimpish*
Mozjs78Ubuntujammy*
Mozjs78Ubuntukinetic*
Mozjs78Ubuntulunar*
Mozjs78Ubuntuupstream*
Rust-crossbeam-utilsUbuntuesm-apps/focal*
Rust-crossbeam-utilsUbuntuesm-apps/jammy*
Rust-crossbeam-utilsUbuntufocal*
Rust-crossbeam-utilsUbuntuimpish*
Rust-crossbeam-utilsUbuntujammy*
Rust-crossbeam-utilsUbuntukinetic*
Rust-crossbeam-utilsUbuntuupstream*
Rust-crossbeam-utils-0.7Ubuntuesm-apps/jammy*
Rust-crossbeam-utils-0.7Ubuntujammy*
Rust-crossbeam-utils-0.7Ubuntukinetic*
RustcUbuntubionic*
RustcUbuntuesm-apps/focal*
RustcUbuntuesm-apps/xenial*
RustcUbuntuesm-infra-legacy/trusty*
RustcUbuntufocal*
RustcUbuntuimpish*
RustcUbuntujammy*
RustcUbuntukinetic*
RustcUbuntutrusty*
RustcUbuntutrusty/esm*
RustcUbuntuxenial*
ThunderbirdUbuntubionic*
ThunderbirdUbuntudevel*
ThunderbirdUbuntufocal*
ThunderbirdUbuntuimpish*
ThunderbirdUbuntujammy*
ThunderbirdUbuntukinetic*
ThunderbirdUbuntulunar*
ThunderbirdUbuntumantic*
ThunderbirdUbuntunoble*
ThunderbirdUbuntuoracular*
ThunderbirdUbuntuplucky*
ThunderbirdUbuntuquesting*
ThunderbirdUbuntutrusty*
ThunderbirdUbuntuxenial*

Extended Description

A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:

A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Potential Mitigations

  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
  • Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use