ApexPro/CARESCAPE Telemetry Server up to 4.2 Configuration File Key credentials storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ApexPro/CARESCAPE Telemetry Server up to 4.2. It has been classified as problematic. This issue affects some unknown processing of the component Configuration File. This manipulation causes credentials storage (Key). The identification of this vulnerability is CVE-2020-6961. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability classified as problematic was found in ApexPro/CARESCAPE Telemetry Server up to 4.2. Affected by this vulnerability is an unknown code block of the component Configuration File. The manipulation with an unknown input leads to a credentials storage vulnerability (Key). The CWE definition for the vulnerability is CWE-256. Storing a password in plaintext may result in a system compromise. As an impact it is known to affect confidentiality. The summary by CVE is:
In ApexPro Telemetry Server, Versions 4.2 and prior, CARESCAPE Telemetry Server v4.2 & prior, Clinical Information Center (CIC) Versions 4.X and 5.X, CARESCAPE Telemetry Server Version 4.3, CARESCAPE Central Station (CSCS) Versions 1.X, a vulnerability exists in the affected products that could allow an attacker to obtain access to the SSH private key in configuration files.
The weakness was shared 01/24/2020. This vulnerability is known as CVE-2020-6961 since 01/14/2020. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-149333, VDB-149332, VDB-149331 and VDB-149330 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: KeyClass: Credentials storage / Key
CWE: CWE-256 / CWE-255
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: 🔍
0-Day Time: 🔍
Timeline
01/14/2020 🔍01/24/2020 🔍
01/25/2020 🔍
03/26/2024 🔍
Sources
Advisory: us-cert.govStatus: Not defined
CVE: CVE-2020-6961 (🔍)
GCVE (CVE): GCVE-0-2020-6961
GCVE (VulDB): GCVE-100-149329
See also: 🔍
Entry
Created: 01/25/2020 08:50Updated: 03/26/2024 08:43
Changes: 01/25/2020 08:50 (37), 01/25/2020 08:55 (17), 03/26/2024 08:43 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.