RAVPower FileHub 2.000.056 HTTP Request information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in RAVPower FileHub 2.000.056. The impacted element is an unknown function. This manipulation as part of HTTP Request causes information disclosure. This vulnerability is registered as CVE-2018-5319. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability has been found in RAVPower FileHub 2.000.056 and classified as problematic. Affected by this vulnerability is some unknown processing. The manipulation as part of a HTTP Request leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
RAVPower FileHub 2.000.056 allows remote users to steal sensitive information via a crafted HTTP request.
The bug was discovered 01/23/2018. The weakness was published 01/24/2018 as EDB-ID 43856 as not defined exploit (Exploit-DB). The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2018-5319 since 01/09/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
After immediately, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. 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.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (43856). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
01/09/2018 🔍01/23/2018 🔍
01/24/2018 🔍
01/24/2018 🔍
01/24/2018 🔍
01/24/2018 🔍
01/25/2018 🔍
07/27/2024 🔍
Sources
Advisory: EDB-ID 43856Status: Not defined
CVE: CVE-2018-5319 (🔍)
GCVE (CVE): GCVE-0-2018-5319
GCVE (VulDB): GCVE-100-112405
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/25/2018 08:17Updated: 07/27/2024 15:27
Changes: 01/25/2018 08:17 (64), 12/27/2019 13:22 (1), 07/27/2024 15:27 (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.