Leptonica through 1.75.3 uses hardcoded /tmp pathnames, which might allow local users to overwrite arbitrary files or have unspecified other impact by creating files in advance or winning a race condition, as demonstrated by /tmp/junk_split_image.ps in prog/splitimage2pdf.c.
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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Leptonica | Leptonica | * | 1.75.3 (including) |
| Leptonlib | Ubuntu | artful | * |
| Leptonlib | Ubuntu | bionic | * |
| Leptonlib | Ubuntu | cosmic | * |
| Leptonlib | Ubuntu | devel | * |
| Leptonlib | Ubuntu | disco | * |
| Leptonlib | Ubuntu | eoan | * |
| Leptonlib | Ubuntu | esm-apps/bionic | * |
| Leptonlib | Ubuntu | esm-apps/focal | * |
| Leptonlib | Ubuntu | esm-apps/jammy | * |
| Leptonlib | Ubuntu | esm-apps/noble | * |
| Leptonlib | Ubuntu | esm-apps/xenial | * |
| Leptonlib | Ubuntu | esm-infra-legacy/trusty | * |
| Leptonlib | Ubuntu | focal | * |
| Leptonlib | Ubuntu | groovy | * |
| Leptonlib | Ubuntu | hirsute | * |
| Leptonlib | Ubuntu | impish | * |
| Leptonlib | Ubuntu | jammy | * |
| Leptonlib | Ubuntu | kinetic | * |
| Leptonlib | Ubuntu | lunar | * |
| Leptonlib | Ubuntu | mantic | * |
| Leptonlib | Ubuntu | noble | * |
| Leptonlib | Ubuntu | oracular | * |
| Leptonlib | Ubuntu | plucky | * |
| Leptonlib | Ubuntu | questing | * |
| Leptonlib | Ubuntu | trusty | * |
| Leptonlib | Ubuntu | trusty/esm | * |
| Leptonlib | Ubuntu | xenial | * |
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.