VYPR

CWE-362

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

ClassDraftLikelihood: Medium

Description

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.

Hierarchy (View 1000)

Related attack patterns (CAPEC)

CAPEC-26 · CAPEC-29

CVEs mapped to this weakness (2,607)

page 47 of 131
  • CVE-2021-40490HigSep 3, 2021
    risk 0.46cvss 7.0epss 0.00

    A race condition was discovered in ext4_write_inline_data_end in fs/ext4/inline.c in the ext4 subsystem in the Linux kernel through 5.13.13.

  • CVE-2021-31004HigAug 24, 2021
    risk 0.46cvss 7.0epss 0.00

    A race condition was addressed with improved locking. This issue is fixed in macOS Monterey 12.0.1, macOS Big Sur 11.5. An application may be able to gain elevated privileges.

  • CVE-2021-30996HigAug 24, 2021
    risk 0.46cvss 7.0epss 0.01

    A race condition was addressed with improved state handling. This issue is fixed in macOS Monterey 12.1, iOS 15.2 and iPadOS 15.2. A malicious application may be able to execute arbitrary code with kernel privileges.

  • CVE-2021-30995HigAug 24, 2021
    risk 0.46cvss 7.0epss 0.02

    A race condition was addressed with improved state handling. This issue is fixed in macOS Big Sur 11.6.2, tvOS 15.2, macOS Monterey 12.1, Security Update 2021-008 Catalina, iOS 15.2 and iPadOS 15.2, watchOS 8.3. A malicious application may be able to elevate privileges.

  • CVE-2021-30955HigAug 24, 2021
    risk 0.46cvss 7.0epss 0.05

    A race condition was addressed with improved state handling. This issue is fixed in macOS Monterey 12.1, watchOS 8.3, iOS 15.2 and iPadOS 15.2, tvOS 15.2. A malicious application may be able to execute arbitrary code with kernel privileges.

  • CVE-2021-30933HigAug 24, 2021
    risk 0.46cvss 7.0epss 0.01

    A race condition was addressed with improved state handling. This issue is fixed in macOS Monterey 12.0.1, macOS Big Sur 11.6. A malicious application may be able to execute arbitrary code with kernel privileges.

  • CVE-2021-30923HigAug 24, 2021
    risk 0.46cvss 7.0epss 0.01

    A race condition was addressed with improved locking. This issue is fixed in macOS Monterey 12.0.1. A malicious application may be able to execute arbitrary code with kernel privileges.

  • CVE-2021-30899HigAug 24, 2021
    risk 0.46cvss 7.0epss 0.01

    A race condition was addressed with improved state handling. This issue is fixed in macOS Monterey 12.0.1, Security Update 2021-007 Catalina, macOS Big Sur 11.6.1. A malicious application may be able to execute arbitrary code with kernel privileges.

  • CVE-2021-30868HigAug 24, 2021
    risk 0.46cvss 7.0epss 0.01

    A race condition was addressed with improved locking. This issue is fixed in macOS Monterey 12.0.1, macOS Big Sur 11.6.1. A malicious application may be able to execute arbitrary code with kernel privileges.

  • CVE-2021-30857HigAug 24, 2021
    risk 0.46cvss 7.0epss 0.01

    A race condition was addressed with improved locking. This issue is fixed in Security Update 2021-005 Catalina, iOS 14.8 and iPadOS 14.8, tvOS 15, iOS 15 and iPadOS 15, watchOS 8, macOS Big Sur 11.6. A malicious application may be able to execute arbitrary code with kernel…

  • CVE-2020-36462HigAug 8, 2021
    risk 0.46cvss 8.1epss 0.01

    An issue was discovered in the syncpool crate before 0.1.6 for Rust. There is an unconditional implementation of Send for Bucket2.

  • CVE-2020-36457HigAug 8, 2021
    risk 0.46cvss 8.1epss 0.01

    An issue was discovered in the lever crate before 0.1.1 for Rust. AtomicBox implements the Send and Sync traits for all types T.

  • CVE-2020-36455HigAug 8, 2021
    risk 0.46cvss 8.1epss 0.01

    An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock unconditionally implements Send and Sync.

  • CVE-2020-36447HigAug 8, 2021
    risk 0.46cvss 8.1epss 0.01

    An issue was discovered in the v9 crate through 2020-12-18 for Rust. There is an unconditional implementation of Sync for SyncRef.

  • CVE-2020-36441HigAug 8, 2021
    risk 0.46cvss 8.1epss 0.01

    An issue was discovered in the abox crate before 0.4.1 for Rust. It implements Send and Sync for AtomicBox with no requirement for T: Send and T: Sync.

  • CVE-2020-36440HigAug 8, 2021
    risk 0.46cvss 8.1epss 0.01

    An issue was discovered in the libsbc crate before 0.1.5 for Rust. For Decoder, it implements Send for any R: Read.

  • CVE-2020-36439HigAug 8, 2021
    risk 0.46cvss 8.1epss 0.01

    An issue was discovered in the ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket and WriteTicket.

  • CVE-2020-36438HigAug 8, 2021
    risk 0.46cvss 8.1epss 0.01

    An issue was discovered in the tiny_future crate before 0.4.0 for Rust. Future does not have bounds on its Send and Sync traits.

  • CVE-2020-36437HigAug 8, 2021
    risk 0.46cvss 8.1epss 0.01

    An issue was discovered in the conqueue crate before 0.4.0 for Rust. There are unconditional implementations of Send and Sync for QueueSender.

  • CVE-2020-36436HigAug 8, 2021
    risk 0.46cvss 8.1epss 0.01

    An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab and Unordered<T, S> do not have bounds on their Send and Sync traits.