baijiacms V3 index.php?mod=mobile&name=member&do=index Request Path information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in baijiacms V3 and classified as problematic. The affected element is an unknown function of the file index.php?mod=mobile&name=member&do=index. The manipulation as part of Request leads to information disclosure (Path). This vulnerability is listed as CVE-2018-10219. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as problematic, has been found in baijiacms V3. This issue affects an unknown part of the file index.php?mod=mobile&name=member&do=index. The manipulation as part of a Request leads to a information disclosure vulnerability (Path). Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
baijiacms V3 has physical path leakage via an index.php?mod=mobile&name=member&do=index request.
The bug was discovered 04/19/2018. The weakness was presented 04/19/2018 (Website). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2018-10219 since 04/19/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: PathClass: Information disclosure / Path
CWE: CWE-200 / CWE-284 / CWE-266
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: no mitigation knownStatus: 🔍
Timeline
04/19/2018 🔍04/19/2018 🔍
04/19/2018 🔍
04/19/2018 🔍
04/21/2018 🔍
01/30/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-10219 (🔍)
GCVE (CVE): GCVE-0-2018-10219
GCVE (VulDB): GCVE-100-116903
Entry
Created: 04/21/2018 18:35Updated: 01/30/2020 09:35
Changes: 04/21/2018 18:35 (57), 01/30/2020 09:35 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.