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,712)

page 14 of 136
  • CVE-2018-13903HigSep 8, 2020
    risk 0.53cvss 8.1epss 0.01

    u'Error in UE due to race condition in EPCO handling' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in APQ8053, MDM9205, MDM9206, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, SDM450,…

  • CVE-2020-12387HigMay 26, 2020
    risk 0.53cvss 8.1epss 0.01

    A race condition when running shutdown code for Web Worker led to a use-after-free vulnerability. This resulted in a potentially exploitable crash. This vulnerability affects Firefox ESR < 68.8, Firefox < 76, and Thunderbird < 68.8.0.

  • CVE-2020-5876HigApr 30, 2020
    risk 0.53cvss 8.1epss 0.01

    On BIG-IP 15.0.0-15.0.1.3, 14.1.0-14.1.2.3, 13.1.0-13.1.3.3, 12.1.0-12.1.5.1, and 11.6.1-11.6.5.1, a race condition exists where mcpd and other processes may make unencrypted connection attempts to a new configuration sync peer. The race condition can occur when changing the…

  • CVE-2018-21040HigApr 8, 2020
    risk 0.53cvss 8.1epss 0.00

    An issue was discovered on Samsung mobile devices with O(8.x) and P(9.0) (Exynos 9810 chipsets) software. There is a race condition with a resultant use-after-free in the g2d driver. The Samsung ID is SVE-2018-12959 (December 2018).

  • CVE-2018-21086HigApr 8, 2020
    risk 0.53cvss 8.1epss 0.00

    An issue was discovered on Samsung mobile devices with L(5.x), M(6.0), and N(7.x) software. There is a race condition with a resultant double free in vnswap_init_backing_storage. The Samsung ID is SVE-2017-11177 (February 2018).

  • CVE-2018-21085HigApr 8, 2020
    risk 0.53cvss 8.1epss 0.00

    An issue was discovered on Samsung mobile devices with L(5.x), M(6.0), and N(7.x) software. There is a race condition with a resultant use-after-free in vnswap_deinit_backing_storage. The Samsung ID is SVE-2017-11176 (February 2018).

  • CVE-2018-21084HigApr 8, 2020
    risk 0.53cvss 8.1epss 0.00

    An issue was discovered on Samsung mobile devices with L(5.1), M(6.0), and N(7.x) software. There is a race condition with a resultant read-after-free issue in get_kek. The Samsung ID is SVE-2017-11174 (February 2018).

  • CVE-2017-18647HigApr 7, 2020
    risk 0.53cvss 8.1epss 0.00

    An issue was discovered on Samsung mobile devices with M(6,x) and N(7.0) software. The TA Scrypto v1.0 implementation in Secure Driver has a race condition with a resultant buffer overflow. The Samsung IDs are SVE-2017-8973, SVE-2017-8974, and SVE-2017-8975 (November 2017).

  • CVE-2017-18692HigApr 7, 2020
    risk 0.53cvss 8.1epss 0.00

    An issue was discovered on Samsung mobile devices with M(6.0) and N(7.0) (MSM8939, MSM8996, MSM8998, Exynos7580, Exynos8890, or Exynos8895 chipsets) software. There is a race condition, with a resultant buffer overflow, in the sec_ts touchscreen sysfs interface. The Samsung ID…

  • CVE-2016-11030HigApr 7, 2020
    risk 0.53cvss 8.1epss 0.00

    An issue was discovered on Samsung mobile devices with KK(4.4), L(5.0/5.1), and M(6.0) (with Hrm sensor support) software. The sysfs of the MAX86902 sensor driver does not prevent concurrent access, leading to a race condition and resultant heap-based buffer overflow. The…

  • CVE-2019-20568HigMar 24, 2020
    risk 0.53cvss 8.1epss 0.00

    An issue was discovered on Samsung mobile devices with O(8.x) and P(9.0) devices (Exynos and Qualcomm chipsets) software. A race condition causes a Use-After-Free. The Samsung ID is SVE-2019-15067 (September 2019).

  • CVE-2019-11215HigFeb 14, 2020
    risk 0.53cvss 8.1epss 0.01

    In Combodo iTop 2.2.0 through 2.6.0, if the configuration file is writable, then execution of arbitrary code can be accomplished by calling ajax.dataloader with a maliciously crafted payload. Many conditions can place the configuration file into a writable state: during…

  • CVE-2014-3701HigDec 15, 2019
    risk 0.53cvss 8.1epss 0.01

    eDeploy has tmp file race condition flaws

  • CVE-2019-19017HigDec 2, 2019
    risk 0.53cvss 8.1epss 0.01

    An issue was discovered in TitanHQ WebTitan before 5.18. The appliance has a hard-coded root password set during installation. An attacker could utilize this to gain root privileges on the system.

  • CVE-2009-4011HigNov 9, 2019
    risk 0.53cvss 8.1epss 0.01

    dtc-xen 0.5.x before 0.5.4 suffers from a race condition where an attacker could potentially get a bash access as xenXX user on the dom0, and then access a potentially reuse an already opened VPS console.

  • CVE-2006-4245HigNov 6, 2019
    risk 0.53cvss 8.1epss 0.01

    archivemail 0.6.2 uses temporary files insecurely leading to a possible race condition.

  • CVE-2005-2352HigNov 1, 2019
    risk 0.53cvss 8.1epss 0.01

    I race condition in Temp files was found in gs-gpl before 8.56 addons scripts.

  • CVE-2019-8162HigOct 17, 2019
    risk 0.53cvss 8.1epss 0.02

    Adobe Acrobat and Reader versions , 2019.012.20040 and earlier, 2017.011.30148 and earlier, 2017.011.30148 and earlier, 2015.006.30503 and earlier, and 2015.006.30503 and earlier have a race condition vulnerability. Successful exploitation could lead to arbitrary code execution .

  • CVE-2019-12263HigAug 9, 2019
    risk 0.53cvss 8.1epss 0.03

    Wind River VxWorks 6.9.4 and vx7 has a Buffer Overflow in the TCP component (issue 4 of 4). There is an IPNET security vulnerability: TCP Urgent Pointer state confusion due to race condition.

  • CVE-2019-9821HigJul 23, 2019
    risk 0.53cvss 8.1epss 0.01

    A use-after-free vulnerability can occur in AssertWorkerThread due to a race condition with shared workers. This results in a potentially exploitable crash. This vulnerability affects Firefox < 67.