Medtronic MyCareLink Patient Monitor 24952 cleartext storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Medtronic MyCareLink Patient Monitor 24950 and MyCareLink Patient Monitor 24952. The impacted element is an unknown function. The manipulation leads to cleartext storage. This vulnerability is traded as CVE-2025-4394. It is possible to launch the attack on the physical device. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Medtronic MyCareLink Patient Monitor 24950 and MyCareLink Patient Monitor 24952 (the affected version is unknown) and classified as problematic. This issue affects an unknown code. The manipulation with an unknown input leads to a cleartext storage vulnerability. Using CWE to declare the problem leads to CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. Impacted is confidentiality. The summary by CVE is:
Medtronic MyCareLink Patient Monitor uses an unencrypted filesystem on internal storage, which allows an attacker with physical access to read and modify files. This issue affects MyCareLink Patient Monitor models 24950 and 24952: before June 25, 2025
The weakness was shared by Ethan Morchy. The advisory is shared at global.medtronic.com. The identification of this vulnerability is CVE-2025-4394 since 05/06/2025. The exploitation is known to be easy. 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 T1555 for this issue.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-22512). 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: 4.6VulDB Meta Temp Score: 4.5
VulDB Base Score: 2.4
VulDB Temp Score: 2.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.8
CNA Vector (Medtronic): 🔒
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: Cleartext storageCWE: CWE-312 / CWE-310
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
05/06/2025 CVE reserved07/24/2025 Advisory disclosed
07/24/2025 VulDB entry created
03/27/2026 VulDB entry last update
Sources
Advisory: global.medtronic.comResearcher: Ethan Morchy
Status: Confirmed
CVE: CVE-2025-4394 (🔒)
GCVE (CVE): GCVE-0-2025-4394
GCVE (VulDB): GCVE-100-317489
EUVD: 🔒
Entry
Created: 07/24/2025 09:18Updated: 03/27/2026 21:49
Changes: 07/24/2025 09:18 (63), 07/24/2025 16:17 (1), 03/27/2026 21:49 (1)
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.