If an X.509 certificate contains a malformed policy constraint and policy processing is enabled, then a write lock will be taken twice recu…
If an X.509 certificate contains a malformed policy constraint and policy processing is enabled, then a write lock will be taken twice recursively. On some operating systems (most widely: Windows) this results in a denial of service when the affected process hangs. Policy processing being enabled on a publicly facing server is not considered to be a common setup. Policy processing is enabled by passing the `-policy' argument to the command line utilities or by calling the `X509_VERIFY_PARAM_set1_policies()' function. Update (31 March 2023): The description of the policy processing enablement was corrected based on CVE-2023-0466.
The product uses double-checked locking to access a resource without the overhead of explicit synchronization, but the locking is insufficient.
https://cwe.mitre.org/data/definitions/609.html →Open in CWE collection →The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
https://cwe.mitre.org/data/definitions/667.html →Open in CWE collection →The adversary triggers and exploits a deadlock condition in the target software to cause a denial of service. A deadlock can occur when two or more competing actions are waiting for each other to finish, and thus neither ever does. Deadlock conditions can be difficult to detect.
https://capec.mitre.org/data/definitions/25.html →Open in CAPEC collection →The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
https://capec.mitre.org/data/definitions/26.html →Open in CAPEC collection →This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to them. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file they will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file.
https://capec.mitre.org/data/definitions/27.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| Tracked | ||
| Tracked | ||
| edk2 | Tracked | |
| edk2 | Tracked | |
| edk2 | Tracked | |
| edk2 | Tracked | |
| edk2 | Tracked | |
| edk2 | Tracked | |
| edk2 | Tracked | |
| edk2 | Tracked | |
| edk2 | Tracked | |
| edk2 | Tracked | |
| edk2 | Tracked | |
| edk2 | Tracked | |
| nodejs | Tracked | |
| nodejs | Tracked | |
| nodejs | Tracked | |
| nodejs | Tracked | |
| nodejs | Tracked | |
| nodejs | Tracked |