Medtronic MyCareLink Patient Monitor hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Medtronic MyCareLink Patient Monitor, 24950 MyCareLink Monitor and 24952 MyCareLink Monitor. It has been classified as critical. Affected by this issue is some unknown functionality. The manipulation leads to hard-coded credentials. This vulnerability is traded as CVE-2018-8870. It is possible to launch the attack on the physical device. There is no exploit available.
Details
A vulnerability was found in Medtronic MyCareLink Patient Monitor, 24950 MyCareLink Monitor and 24952 MyCareLink Monitor (unknown version) and classified as critical. This issue affects an unknown code block. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. Using CWE to declare the problem leads to CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Medtronic MyCareLink Patient Monitor, 24950 MyCareLink Monitor, all versions, and 24952 MyCareLink Monitor, all versions contains a hard-coded operating system password. An attacker with physical access can remove the case of the device, connect to the debug port, and use the password to gain privileged access to the operating system.
The bug was discovered 06/28/2018. The weakness was shared 07/03/2018 (Website). The advisory is shared at ics-cert.us-cert.gov. The identification of this vulnerability is CVE-2018-8870 since 03/20/2018. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 4 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 entry VDB-120208 is related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.8VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.8
NVD Vector: 🔍
CNA Base Score: 6.4
CNA 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: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
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
03/20/2018 🔍06/28/2018 🔍
07/02/2018 🔍
07/03/2018 🔍
07/03/2018 🔍
05/22/2025 🔍
Sources
Advisory: ics-cert.us-cert.govStatus: Not defined
CVE: CVE-2018-8870 (🔍)
GCVE (CVE): GCVE-0-2018-8870
GCVE (VulDB): GCVE-100-120209
See also: 🔍
Entry
Created: 07/03/2018 17:48Updated: 05/22/2025 22:09
Changes: 07/03/2018 17:48 (56), 02/24/2020 10:41 (1), 05/22/2025 22:09 (28)
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.