{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2022-41627 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41627 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-41627 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2022-41627 in the wild and no public exploit code.\n\nAffected product: AliveCor KardiaMobile. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-41627/ (Markdown: https://insights.sbomify.com/CVE-2022-41627/index.md)","id":"CVE-2022-41627","markdown":"https://insights.sbomify.com/CVE-2022-41627/index.md","name":"CVE-2022-41627","record":{"aliases":["GHSA-4x7m-cpcp-9gfm"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Personal EKG device","requires_auth":"none","summary":"Attackers within close proximity can intercept unencrypted EKG data or disrupt device functionality via acoustic interference.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"kardiamobile_6l_firmware","vendor":"alivecor"},{"product":"kardiamobile_card_firmware","vendor":"alivecor"},{"product":"kardiamobile_firmware","vendor":"alivecor"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in KardiaMobile","id":"CVE-2022-41627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Intel(R) NUC P14E Laptop Element software for Windows 10","id":"CVE-2022-41628"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused","id":"CVE-2022-41626"},"products":["KardiaMobile"],"published":"2022-10-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-16","vendors":["AliveCor"]},"summary":"Attackers within close proximity can intercept unencrypted EKG data or disrupt device functionality via acoustic interference.","url":"https://insights.sbomify.com/CVE-2022-41627/"}