Kyocera TASKalfa 4002i/TASKalfa 6002i DoBox_CstmBox_Info.model.htm HTTP Request information disclosure
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Kyocera TASKalfa 4002i and TASKalfa 6002i. It has been classified as problematic. This affects an unknown part of the file DoBox_CstmBox_Info.model.htm. The manipulation as part of HTTP Request leads to information disclosure. This vulnerability is uniquely identified as CVE-2018-16656. It is possible to initiate the attack remotely. There is no exploit available. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Details
A vulnerability was found in Kyocera TASKalfa 4002i and TASKalfa 6002i (unknown version) and classified as problematic. Affected by this issue is an unknown code block of the file DoBox_CstmBox_Info.model.htm. The manipulation as part of a HTTP Request leads to a information disclosure vulnerability. 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. CVE summarizes:
DoBox_CstmBox_Info.model.htm on Kyocera TASKalfa 4002i and 6002i devices allows remote attackers to read the documents of arbitrary users via a modified HTTP request.
The weakness was shared 05/14/2019. This vulnerability is handled as CVE-2018-16656 since 09/07/2018. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
By approaching the search of inurl:DoBox_CstmBox_Info.model.htm 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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: 🔍
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
09/07/2018 🔍05/14/2019 🔍
05/15/2019 🔍
09/19/2023 🔍
Sources
Advisory: mars-cheng.github.ioStatus: Not defined
CVE: CVE-2018-16656 (🔍)
GCVE (CVE): GCVE-0-2018-16656
GCVE (VulDB): GCVE-100-135014
Entry
Created: 05/15/2019 10:12 AMUpdated: 09/19/2023 11:49 AM
Changes: 05/15/2019 10:12 AM (35), 06/12/2020 09:23 AM (17), 09/19/2023 11:49 AM (3)
Complete: 🔍
Cache ID: 18:00B:40
No comments yet. Languages: en.
Please log in to comment.