CVE Vulnerabilities

CVE-2016-0764

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

Published: Jul 17, 2017 | Modified: Apr 20, 2025
CVSS 3.x
6.2
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
2.1 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V3
Ubuntu
LOW

Race condition in Network Manager before 1.0.12 as packaged in Red Hat Enterprise Linux Desktop 7, Red Hat Enterprise Linux HPC Node 7, Red Hat Enterprise Linux Server 7, and Red Hat Enterprise Linux Workstation 7 allows local users to obtain sensitive connection information by reading temporary files during ifcfg and keyfile changes.

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
Networkmanager Redhat * 1.0.8 (including)
Red Hat Enterprise Linux 7 RedHat libnl3-0:3.2.28-2.el7 *
Red Hat Enterprise Linux 7 RedHat NetworkManager-1:1.4.0-12.el7 *
Red Hat Enterprise Linux 7 RedHat network-manager-applet-0:1.4.0-2.el7 *
Red Hat Enterprise Linux 7 RedHat NetworkManager-libreswan-0:1.2.4-1.el7 *
Network-manager Ubuntu precise *
Network-manager Ubuntu trusty *
Network-manager Ubuntu upstream *
Network-manager Ubuntu vivid/stable-phone-overlay *
Network-manager Ubuntu wily *
Network-manager Ubuntu yakkety *
Network-manager 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