A race condition was found in the mkhomedir tool shipped with the oddjob package in versions before 0.34.5 and 0.34.6 wherein, during the home creation, mkhomedir copies the /etc/skel directory into the newly created home and changes its ownership to the homes user without properly checking the homedir path. This flaw allows an attacker to leverage this issue by creating a symlink point to a target folder, which then has its ownership transferred to the new home directorys unprivileged user.
The product contains a code sequence that can run concurrently with other code, and the code sequence 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 that is operating concurrently.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Oddjob | Redhat | * | 0.34.5 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | oddjob-0:0.34.5-3.el8 | * |
| Oddjob | Ubuntu | bionic | * |
| Oddjob | Ubuntu | eoan | * |
| Oddjob | Ubuntu | esm-apps/bionic | * |
| Oddjob | Ubuntu | esm-apps/focal | * |
| Oddjob | Ubuntu | esm-apps/xenial | * |
| Oddjob | Ubuntu | focal | * |
| Oddjob | Ubuntu | trusty | * |
| Oddjob | Ubuntu | upstream | * |
| Oddjob | Ubuntu | xenial | * |
This can have security implications when the expected synchronization is in security-critical code, such as recording whether a user is authenticated or modifying important state information that should not be influenced by an outsider. A race condition occurs within concurrent environments, and 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. Programmers may assume that certain code sequences execute too quickly to be affected by an interfering code sequence; when they are not, this violates atomicity. For example, the single “x++” statement may appear atomic at the code layer, but it is actually non-atomic at the instruction layer, since it involves a read (the original value of x), followed by a computation (x+1), followed by a write (save the result to x). 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.