CVE Vulnerabilities

CVE-2016-1000236

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

Published: Nov 19, 2019 | Modified: Nov 21, 2024
CVSS 3.x
4.4
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
3.5 LOW
AV:N/AC:M/Au:S/C:P/I:N/A:N
RedHat/V2
3.5 MODERATE
AV:N/AC:M/Au:S/C:P/I:N/A:N
RedHat/V3
5.4 MODERATE
CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N
Ubuntu
NEGLIGIBLE

Node-cookie-signature before 1.0.6 is affected by a timing attack due to the type of comparison used.

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

Name Vendor Start Version End Version
Cookie-signature Cookie-signature_project * 1.0.6 (excluding)
Node-cookie-signature Ubuntu artful *
Node-cookie-signature Ubuntu bionic *
Node-cookie-signature Ubuntu cosmic *
Node-cookie-signature Ubuntu esm-apps/bionic *
Node-cookie-signature Ubuntu esm-apps/xenial *
Node-cookie-signature Ubuntu trusty *
Node-cookie-signature Ubuntu xenial *
Node-cookie-signature Ubuntu yakkety *
Node-cookie-signature Ubuntu zesty *

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