Nagios XI 5.5.6 api_tool.php host Reflected cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Nagios XI 5.5.6. It has been rated as problematic. This affects an unknown function of the file api_tool.php. This manipulation of the argument host as part of Parameter causes cross site scripting (Reflected). This vulnerability is registered as CVE-2018-15712. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability has been found in Nagios XI 5.5.6 (Log Management Software) and classified as problematic. Affected by this vulnerability is an unknown function of the file api_tool.php. The manipulation of the argument host as part of a Parameter leads to a cross site scripting vulnerability (Reflected). The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is:
Nagios XI 5.5.6 allows reflected cross site scripting from remote unauthenticated attackers via the host parameter in api_tool.php.
The bug was discovered 11/13/2018. The weakness was published 11/14/2018 (Website). The advisory is shared at tenable.com. This vulnerability is known as CVE-2018-15712 since 08/22/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:api_tool.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-126801, VDB-126802, VDB-126804 and VDB-126806. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
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
Name: ReflectedClass: Cross site scripting / Reflected
CWE: CWE-79 / CWE-94 / CWE-74
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/22/2018 🔍11/13/2018 🔍
11/14/2018 🔍
11/14/2018 🔍
11/15/2018 🔍
04/12/2020 🔍
Sources
Advisory: tenable.comStatus: Not defined
CVE: CVE-2018-15712 (🔍)
GCVE (CVE): GCVE-0-2018-15712
GCVE (VulDB): GCVE-100-126805
scip Labs: https://www.scip.ch/en/?labs.20150108
See also: 🔍
Entry
Created: 11/15/2018 07:52Updated: 04/12/2020 17:18
Changes: 11/15/2018 07:52 (63), 04/12/2020 17:18 (1)
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.