Centreon up to 18.10.7/19.10.0 call.php cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Centreon up to 18.10.7/19.10.0. This affects an unknown part of the file centreon-autodiscovery-server/views/scan/ajax/call.php. Performing a manipulation results in cross-site request forgery. This vulnerability was named CVE-2019-17642. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Centreon up to 18.10.7/19.10.0. This affects some unknown processing of the file centreon-autodiscovery-server/views/scan/ajax/call.php. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:
An issue was discovered in Centreon before 18.10.8, 19.10.1, and 19.04.2. It allows CSRF with resultant remote command execution via shell metacharacters in a POST to centreon-autodiscovery-server/views/scan/ajax/call.php in the Autodiscovery plugin.
The weakness was presented 03/05/2020 (Website). The advisory is shared at documentation.centreon.com. This vulnerability is uniquely identified as CVE-2019-17642 since 10/16/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
By approaching the search of inurl:centreon-autodiscovery-server/views/scan/ajax/call.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 18.10.8 or 19.10.1 eliminates this vulnerability.
See VDB-150936, VDB-150935 and VDB-150934 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 18.10.0
- 18.10.1
- 18.10.2
- 18.10.3
- 18.10.4
- 18.10.5
- 18.10.6
- 18.10.7
- 19.0
- 19.1
- 19.2
- 19.3
- 19.4
- 19.5
- 19.6
- 19.7
- 19.8
- 19.9
- 19.10.0
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Centreon 18.10.8/19.10.1
Timeline
10/16/2019 🔍03/05/2020 🔍
03/06/2020 🔍
03/06/2020 🔍
Sources
Advisory: documentation.centreon.comStatus: Not defined
CVE: CVE-2019-17642 (🔍)
GCVE (CVE): GCVE-0-2019-17642
GCVE (VulDB): GCVE-100-150933
See also: 🔍
Entry
Created: 03/06/2020 10:11Updated: 03/06/2020 10:16
Changes: 03/06/2020 10:11 (39), 03/06/2020 10:16 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.