Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2009-4029

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

Published: Dec 20, 2009 | Modified: Apr 09, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
4.4 MEDIUM
AV:L/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
3.7 LOW
AV:L/AC:H/Au:N/C:P/I:P/A:P
RedHat/V3
Ubuntu
LOW
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2009-4029
CWEhttps://cwe.mitre.org/data/definitions/362.html

The (1) dist or (2) distcheck rules in GNU Automake 1.11.1, 1.10.3, and release branches branch-1-4 through branch-1-9, when producing a distribution tarball for a package that uses Automake, assign insecure permissions (777) to directories in the build tree, which introduces a race condition that allows local users to modify the contents of package files, introduce Trojan horse programs, or conduct other attacks before the build is complete.

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
AutomakeGnu1.10.3 (including)1.10.3 (including)
AutomakeGnu1.11.1 (including)1.11.1 (including)
AutomakeGnubranch-1-9 (including)branch-1-9 (including)
Red Hat Enterprise Linux 5RedHatautomake-0:1.9.6-2.3.el5*
Red Hat Enterprise Linux 5RedHatautomake14-0:1.4p6-13.el5.1*
Red Hat Enterprise Linux 5RedHatautomake15-0:1.5-16.el5.2*
Red Hat Enterprise Linux 5RedHatautomake16-0:1.6.3-8.el5.1*
Red Hat Enterprise Linux 5RedHatautomake17-0:1.7.9-7.el5.2*
AutomakeUbuntudapper*
AutomakeUbuntuhardy*
AutomakeUbuntuintrepid*
AutomakeUbuntujaunty*
AutomakeUbuntukarmic*
AutomakeUbuntuupstream*

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