{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-44518 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-44518 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-44518 is a medium-severity vulnerability in n/a, published on 2 Dec 2021. 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-2021-44518 and fix it if it is affected.\n\nWhat it is: CVE-2021-44518 is a medium-severity vulnerability in n/a, published on 2 Dec 2021. 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-2021-44518 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2021-44518/ (Markdown: https://insights.sbomify.com/CVE-2021-44518/index.md)","id":"CVE-2021-44518","markdown":"https://insights.sbomify.com/CVE-2021-44518/index.md","name":"CVE-2021-44518","record":{"aliases":["GHSA-gc5m-6c6c-jvx7"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["account_takeover","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android smart lock app","requires_auth":"none","summary":"An attacker can capture unencrypted pairing codes via Bluetooth to take complete control of the smart lock.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"egeetouch_manager","vendor":"digipas"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"An issue was discovered in the eGeeTouch 3rd Generation Travel Padlock application for Android. The lock sends a pairing code before each operation (lock or unlock) activated via the companion app. The code is sent unencrypted, allowing any attacker with the same app (either Android or iOS) to add the lock and take complete control. For successful exploitation, the attacker must be able to touch the lock's power button, and must be able to capture BLE network communication.","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":"Information disclosure in n/a","id":"CVE-2021-44518","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2021-44519"},"packages":[],"prev":{"headline":"Zoho Desktop Central Authentication Bypass","id":"CVE-2021-44515"},"products":["n/a"],"published":"2021-12-02","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can capture unencrypted pairing codes via Bluetooth to take complete control of the smart lock.","url":"https://insights.sbomify.com/CVE-2021-44518/"}