Heart Health IOS Mobile Application: Uncaught Exception
CVE-2025-24836 is a high-severity uncaught exception vulnerability in Heart Health IOS Mobile Application from Qardio, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected Heart Health IOS Mobile Application versions: 2.7.4. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.24% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Heart Health IOS Mobile Application you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Qardio | Heart Health IOS Mobile Application | 2.7.4 | Not stated |
| Qardio | Heart Health Android Mobile Application | 2.5.1 | Not stated |
| Qardio | QardioARM | All versions | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H. Scored by CNA (hq.dhs.gov).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 6.1 | Medium | CNA (hq.dhs.gov) |
| CVSS 3.1 | 7.1 | High | CNA (hq.dhs.gov) |
Official description
With a specially crafted Python script, an attacker could send continuous startMeasurement commands over an unencrypted Bluetooth connection to the affected device. This would prevent the device from connecting to a clinician's app to take patient readings and ostensibly flood it with requests, resulting in a denial-of-service condition.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Uncaught Exception
An exception is thrown from a function, but it is not caught.
How developers prevent this class of flaw
- The choice between a language which has named or unnamed exceptions needs to be done. While unnamed exceptions exacerbate the chance of not properly dealing with an exception, named exceptions suffer from the up call version of the weak base class problem.
- A language can be used which requires, at compile time, to catch all serious exceptions. However, one must make sure to use the most current version of the API as new exceptions could be added.
- Catch all relevant exceptions. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Uncaught Exception vulnerabilities
- 7.7 High severity
- 7.7 High severity
- 7.7 High severity
- 7.7 High severity
- 8.7 High severity
- 7.5 High severity
Spotted an error? Tell us.