Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-32368: n/a

0
High
VulnerabilityCVE-2024-32368cvecve-2024-32368
Published: Mon Apr 22 2024 (04/22/2024, 00:00:00 UTC)
Source: CVE Database V5

Description

CVE-2024-32368 is a high-severity vulnerability affecting the Agasta Sanketlife 2. 0 Pocket 12-Lead ECG Monitor firmware version 3. 0. It arises from insecure permissions in the Bluetooth Low Energy (BLE) component, allowing a local attacker with low privileges to cause a denial of service (DoS) without user interaction. The vulnerability impacts device availability and confidentiality but does not affect integrity. Exploitation requires local access and low privileges but no user interaction, making it moderately accessible to attackers in proximity. No known exploits are reported in the wild yet, and no patches have been published. Organizations using this medical device should prioritize mitigating this vulnerability to prevent potential disruption of critical health monitoring functions.

AI-Powered Analysis

AILast updated: 02/26/2026, 04:18:36 UTC

Technical Analysis

CVE-2024-32368 identifies an insecure permission vulnerability (CWE-276) in the Bluetooth Low Energy (BLE) component of the Agasta Sanketlife 2.0 Pocket 12-Lead ECG Monitor, specifically firmware version 3.0. This vulnerability allows a local attacker with low privileges to trigger a denial of service (DoS) condition on the device. The root cause is improper permission settings within the BLE implementation, which fails to adequately restrict access to certain functions or resources. As a result, an attacker in physical proximity who can interact with the device's BLE interface can exploit this flaw to disrupt the device's operation, causing it to become unavailable. The CVSS v3.1 base score is 7.3 (high), reflecting the attack vector as adjacent network (local BLE), low attack complexity, low privileges required, no user interaction, and a high impact on confidentiality and availability but no impact on integrity. The vulnerability does not require user interaction, increasing the risk of automated or stealthy exploitation. Although no patches or known exploits are currently available, the critical nature of the device in medical monitoring underscores the importance of addressing this issue promptly.

Potential Impact

The primary impact of this vulnerability is denial of service, which can render the ECG monitor unavailable for patient monitoring. This disruption can delay or prevent critical cardiac health assessments, potentially endangering patient safety. The confidentiality impact is rated high, indicating that sensitive patient data transmitted or stored by the device may be exposed or accessible during exploitation. However, the integrity of the device's data or operation is not affected. Organizations relying on these devices in clinical environments face risks of operational downtime and potential breaches of patient data privacy. Given the medical context, even temporary unavailability can have severe consequences for patient care. The requirement for local access limits the scope somewhat but does not eliminate risk, especially in healthcare settings where devices may be accessible to multiple personnel or visitors. The lack of available patches increases the urgency for interim mitigations.

Mitigation Recommendations

To mitigate CVE-2024-32368, organizations should first isolate the affected ECG monitors within secure network segments to limit BLE access to authorized personnel only. Physical security controls should be enhanced to restrict local access to the devices, including controlled access to patient rooms and device storage areas. Disable or limit BLE functionality when not in active use to reduce the attack surface. Monitor BLE traffic for unusual connection attempts or patterns that could indicate exploitation attempts. Engage with the device vendor to obtain firmware updates or patches as soon as they become available and prioritize their deployment. Implement network-level controls such as BLE device whitelisting and authentication mechanisms if supported by the device. Additionally, establish incident response plans specific to medical device disruptions to ensure rapid recovery and patient safety. Regularly audit device configurations and permissions to detect and remediate insecure settings proactively.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2024-04-12T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6c37b7ef31ef0b56136a

Added to database: 2/25/2026, 9:40:07 PM

Last enriched: 2/26/2026, 4:18:36 AM

Last updated: 2/26/2026, 9:33:19 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats