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
Link | Resource |
---|---|
https://0day.love/itop_vulnerabilities_disclosure.pdf | Broken Link |
https://www.itophub.io/wiki/page?id=2_6_0:release:change_log | Release Notes |
https://0day.love/itop_vulnerabilities_disclosure.pdf | Broken Link |
https://www.itophub.io/wiki/page?id=2_6_0:release:change_log | Release Notes |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 04:20
Type | Values Removed | Values Added |
---|---|---|
References | () https://0day.love/itop_vulnerabilities_disclosure.pdf - Broken Link | |
References | () https://www.itophub.io/wiki/page?id=2_6_0:release:change_log - Release Notes |
Information
Published : 2020-02-14 18:15
Updated : 2024-11-21 04:20
NVD link : CVE-2019-11215
Mitre link : CVE-2019-11215
CVE.ORG link : CVE-2019-11215
JSON object : View
Products Affected
combodo
- itop