ID |
CVE-2020-14059
|
Summary |
An issue was discovered in Squid 5.x before 5.0.3. Due to an Incorrect Synchronization, a Denial of Service can occur when processing objects in an SMP cache because of an Ipc::Mem::PageStack::pop ABA problem during access to the memory page/slot management list. |
References |
|
Vulnerable Configurations |
-
cpe:2.3:a:squid-cache:squid:5.0:*:*:*:*:*:*:*
cpe:2.3:a:squid-cache:squid:5.0:*:*:*:*:*:*:*
-
cpe:2.3:a:squid-cache:squid:5.0.1:*:*:*:*:*:*:*
cpe:2.3:a:squid-cache:squid:5.0.1:*:*:*:*:*:*:*
-
cpe:2.3:a:squid-cache:squid:5.0.2:*:*:*:*:*:*:*
cpe:2.3:a:squid-cache:squid:5.0.2:*:*:*:*:*:*:*
|
CVSS |
Base: | 4.0 (as of 30-03-2021 - 14:43) |
Impact: | |
Exploitability: | |
|
CWE |
CWE-662 |
CAPEC |
-
Leveraging Race Conditions via Symbolic Links
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 her. 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 she 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.
-
Forced Deadlock
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.
-
Leveraging Race Conditions
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 his version and cause the system to read the malicious file.
-
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions
This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.
|
Access |
Vector | Complexity | Authentication |
NETWORK |
LOW |
SINGLE |
|
Impact |
Confidentiality | Integrity | Availability |
NONE |
NONE |
PARTIAL |
|
cvss-vector
via4
|
AV:N/AC:L/Au:S/C:N/I:N/A:P
|
refmap
via4
|
|
Last major update |
30-03-2021 - 14:43 |
Published |
30-06-2020 - 19:15 |
Last modified |
30-03-2021 - 14:43 |