Opsview Monitor Pro up to 4.5.x/4.6.4/5.0.2/5.1.0 HTTP GET Request path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Opsview Monitor Pro up to 4.5.x/4.6.4/5.0.2/5.1.0. Affected by this issue is some unknown functionality. Performing a manipulation as part of HTTP GET Request results in path traversal. This vulnerability is reported as CVE-2016-10367. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Opsview Monitor Pro up to 4.5.x/4.6.4/5.0.2/5.1.0. This affects some unknown processing. The manipulation as part of a HTTP GET Request leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:
In Opsview Monitor Pro (Prior to 5.1.0.162300841, prior to 5.0.2.27475, prior to 4.6.4.162391051, and 4.5.x without a certain 2016 security patch), an unauthenticated Directory Traversal vulnerability can be exploited by issuing a specially crafted HTTP GET request utilizing a simple URL encoding bypass, %252f instead of /.
The bug was discovered 09/01/2016. The weakness was disclosed 05/03/2017 (Website). It is possible to read the advisory at trustwave.com. This vulnerability is uniquely identified as CVE-2016-10367 since 05/03/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 244 days. During that time the estimated underground price was around $0-$5k.
Upgrading eliminates this vulnerability.
The entry VDB-100828 is pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 6.8
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: 🔍
Timeline
09/01/2016 🔍05/03/2017 🔍
05/03/2017 🔍
05/03/2017 🔍
05/03/2017 🔍
09/23/2020 🔍
Sources
Advisory: trustwave.comStatus: Not defined
CVE: CVE-2016-10367 (🔍)
GCVE (CVE): GCVE-0-2016-10367
GCVE (VulDB): GCVE-100-100827
OSVDB: - CVE-2016-10367 - Opsview Monitor Pro - Directory Traversal Issue
See also: 🔍
Entry
Created: 05/03/2017 17:03Updated: 09/23/2020 13:06
Changes: 05/03/2017 17:03 (58), 09/23/2020 13:06 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.