# CVE-2022-40703: Auth bypass in Kardia App

> An attacker with physical access can bypass authentication in the AliveCor Kardia Android app to alter user information.

- **Severity:** Medium 5.2 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **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:** 26 Oct 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-65jr-q7fr-5gcv

## What is CVE-2022-40703?

CVE-2022-40703 is a medium-severity authentication bypass vulnerability in AliveCor Kardia App, published on 26 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CWE-302 Authentication Bypass by Assumed-Immutable Data in AliveCor Kardia App version 5.17.1-754993421 and prior

 on Android allows an unauthenticated attacker with physical access to the Android device containing the app to bypass application authentication and alter information in the app.

Weakness: CWE-287 (Improper Authentication), CWE-302 (Authentication Bypass by Assumed-Immutable Data)

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

It affects 1 product.


Products: Alivecor Kardia.

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

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

## Is CVE-2022-40703 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40703 is a medium-severity authentication bypass vulnerability in AliveCor Kardia App, published on 26 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-40703 in the wild and no public exploit code.

Affected product: AliveCor Kardia App. 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-40703/ (Markdown: https://insights.sbomify.com/CVE-2022-40703/index.md)
```

## Sources

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

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