ID |
CVE-2019-11215
|
Summary |
In Combodo iTop 2.2.0 through 2.6.0, if the configuration file is writable, then execution of arbitrary code can be accomplished by calling ajax.dataloader with a maliciously crafted payload. Many conditions can place the configuration file into a writable state: during installation; during upgrade; in certain cases, an error during modification of the file from the web interface leaves the file writable (can be triggered with XSS); a race condition can be triggered by the hub-connector module (community version only from 2.4.1 to 2.6.0); or editing the file in a CLI. |
References |
|
Vulnerable Configurations |
-
cpe:2.3:a:combodo:itop:2.2.0:*:*:*:community:*:*:*
cpe:2.3:a:combodo:itop:2.2.0:*:*:*:community:*:*:*
-
cpe:2.3:a:combodo:itop:2.2.0:-:*:*:*:*:*:*
cpe:2.3:a:combodo:itop:2.2.0:-:*:*:*:*:*:*
-
cpe:2.3:a:combodo:itop:2.2.0:beta:*:*:*:*:*:*
cpe:2.3:a:combodo:itop:2.2.0:beta:*:*:*:*:*:*
-
cpe:2.3:a:combodo:itop:2.2.1:*:*:*:*:*:*:*
cpe:2.3:a:combodo:itop:2.2.1:*:*:*:*:*:*:*
-
cpe:2.3:a:combodo:itop:2.3.0:-:*:*:*:*:*:*
cpe:2.3:a:combodo:itop:2.3.0:-:*:*:*:*:*:*
-
cpe:2.3:a:combodo:itop:2.3.0:beta:*:*:*:*:*:*
cpe:2.3:a:combodo:itop:2.3.0:beta:*:*:*:*:*:*
-
cpe:2.3:a:combodo:itop:2.3.1:*:*:*:*:*:*:*
cpe:2.3:a:combodo:itop:2.3.1:*:*:*:*:*:*:*
-
cpe:2.3:a:combodo:itop:2.3.2:*:*:*:community:*:*:*
cpe:2.3:a:combodo:itop:2.3.2:*:*:*:community:*:*:*
-
cpe:2.3:a:combodo:itop:2.3.3:*:*:*:*:*:*:*
cpe:2.3:a:combodo:itop:2.3.3:*:*:*:*:*:*:*
-
cpe:2.3:a:combodo:itop:2.3.4:*:*:*:*:*:*:*
cpe:2.3:a:combodo:itop:2.3.4:*:*:*:*:*:*:*
-
cpe:2.3:a:combodo:itop:2.4.0:-:*:*:*:*:*:*
cpe:2.3:a:combodo:itop:2.4.0:-:*:*:*:*:*:*
-
cpe:2.3:a:combodo:itop:2.4.0:beta:*:*:*:*:*:*
cpe:2.3:a:combodo:itop:2.4.0:beta:*:*:*:*:*:*
-
cpe:2.3:a:combodo:itop:2.4.2:*:*:*:community:*:*:*
cpe:2.3:a:combodo:itop:2.4.2:*:*:*:community:*:*:*
-
cpe:2.3:a:combodo:itop:2.6.0:*:*:*:community:*:*:*
cpe:2.3:a:combodo:itop:2.6.0:*:*:*:community:*:*:*
|
CVSS |
Base: | 6.8 (as of 24-08-2020 - 17:37) |
Impact: | |
Exploitability: | |
|
CWE |
CWE-362 |
CAPEC |
-
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 |
MEDIUM |
NONE |
|
Impact |
Confidentiality | Integrity | Availability |
PARTIAL |
PARTIAL |
PARTIAL |
|
cvss-vector
via4
|
AV:N/AC:M/Au:N/C:P/I:P/A:P
|
refmap
via4
|
|
Last major update |
24-08-2020 - 17:37 |
Published |
14-02-2020 - 18:15 |
Last modified |
24-08-2020 - 17:37 |