Jact OpenClinic 0.8.20160412 GET Parameter /shared/view_source.php File information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Jact OpenClinic 0.8.20160412. It has been rated as problematic. The impacted element is an unknown function of the file /shared/view_source.php of the component GET Parameter Handler. The manipulation of the argument File leads to an unknown weakness. This vulnerability is uniquely identified as CVE-2020-20444. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Jact OpenClinic 0.8.20160412 and classified as problematic. This issue affects an unknown function of the file /shared/view_source.php of the component GET Parameter Handler. The manipulation of the argument file with an unknown input leads to a unknown weakness. 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 weakness was disclosed 06/16/2021. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2020-20444. 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.
By approaching the search of inurl:shared/view_source.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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
Website
- Product: https://github.com/jact/openclinic/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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/13/2020 🔍06/16/2021 🔍
06/16/2021 🔍
06/18/2021 🔍
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-20444 (🔍)
GCVE (CVE): GCVE-0-2020-20444
GCVE (VulDB): GCVE-100-177107
Entry
Created: 06/16/2021 20:51Updated: 06/18/2021 20:34
Changes: 06/16/2021 20:51 (36), 06/18/2021 20:34 (3)
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.