# CVE-2022-41627: Weak cryptography in KardiaMobile

> Attackers within close proximity can intercept unencrypted EKG data or disrupt device functionality via acoustic interference.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-4x7m-cpcp-9gfm

## What is CVE-2022-41627?

CVE-2022-41627 is a medium-severity vulnerability in AliveCor KardiaMobile, published on 27 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The physical IoT device of the AliveCor's KardiaMobile, a smartphone-based personal electrocardiogram (EKG) has no encryption for its data-over-sound protocols. Exploiting this vulnerability could allow an attacker to read patient EKG results or create a denial-of-service condition by emitting sounds at similar frequencies as the device, disrupting the smartphone microphone’s ability to accurately read the data. To carry out this attack, the attacker must be close (less than 5 feet) to pick up and emit sound waves.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2022-41627?

It affects 3 products.


Products: Alivecor Kardiamobile 6l Firmware, Alivecor Kardiamobile Card Firmware, Alivecor Kardiamobile Firmware.

## How do I fix CVE-2022-41627?

No fix has been published for CVE-2022-41627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41627 being exploited?

There is no known exploitation of CVE-2022-41627 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41627 and fix it if it is affected.

What it is: CVE-2022-41627 is a medium-severity vulnerability in AliveCor KardiaMobile, published on 27 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41627 in the wild and no public exploit code.

Affected product: AliveCor KardiaMobile. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41627/ (Markdown: https://insights.sbomify.com/CVE-2022-41627/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41627
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41627
- OSV: https://osv.dev/vulnerability/CVE-2022-41627

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41627/
Summaries are generated and may contain mistakes; the official description above is the record.