CVE-2022-40703
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCWE-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe AliveCor Kardia Android app versions 5.17.1-754993421 and prior uses client-side authentication that relies on data stored locally on the Android device which can be modified by an attacker with physical access. This allows bypass of the application's authentication mechanism by altering what the app considers immutable authentication data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.17.1-754993421CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if AliveCor Kardia app is installedCheck the list of installed applications on the Android device for 'AliveCor Kardia' or 'Kardia' using the device settings or an app inventory toolAffected if The app is present on the device
-
Determine installed app versionNavigate to Settings > Apps > AliveCor Kardia > Version info, or use a package manager command like 'adb shell dumpsys package com.alivecor.android.kardia' to retrieve the version name and version codeAffected if The version code is less than or equal to 754993421, or the version name is 5.17.1 or earlier
-
Inspect app authentication storage locationUse ADB to examine the app's shared preferences or database files (typically in /data/data/com.alivecor.android.kardia/) for authentication-related files such as shared_prefs/*.xml or databases/*.db that store credential or session dataAffected if Authentication tokens, session identifiers, or user credentials are found stored in local files that are modifiable without root privileges
-
Verify client-side authentication relianceAnalyze network traffic from the app using a proxy tool; observe whether authentication decisions are made locally based on stored data rather than validated server-side with each requestAffected if The app authenticates based solely on locally stored mutable data without server validation for each protected action
A user is affected if the AliveCor Kardia Android app version 5.17.1-754993421 or earlier is installed and relies on locally stored, modifiable authentication data rather than server-side validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement server-side authentication validation and/or use secure storage mechanisms (Android Keystore) for credential verification rather than relying on mutable local data. Consider adding tamper-detection measures for local authentication state.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40703 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-40703 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data