{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2006-1365 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-1365 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-1365 is a medium-severity authentication bypass vulnerability in n/a, published on 23 Mar 2006. 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-2006-1365 and fix it if it is affected.\n\nWhat it is: CVE-2006-1365 is a medium-severity authentication bypass vulnerability in n/a, published on 23 Mar 2006. 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-2006-1365 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-2006-1365/ (Markdown: https://insights.sbomify.com/CVE-2006-1365/index.md)","id":"CVE-2006-1365","markdown":"https://insights.sbomify.com/CVE-2006-1365/index.md","name":"CVE-2006-1365","record":{"aliases":["GHSA-h53p-r9f5-xvqg"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Motorola mobile phone","requires_auth":"none","summary":"Remote attackers can bypass Bluetooth authentication to add trusted devices and gain AT level access on Motorola phones via a HeloMoto attack.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"e398","vendor":"motorola"},{"product":"pebl_u6","vendor":"motorola"},{"product":"v600","vendor":"motorola"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"The Motorola PEBL U6, the Motorola V600, and possibly the Motorola E398 and other Motorola phones allow remote attackers to add an entry for their own Bluetooth device to a target device's list of trusted devices (aka Device History), and possibly obtain AT level access to the target device, by initiating and interrupting an OBEX Push Profile that pretends to send a vCard, aka a \"HeloMoto\" attack.","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":"Auth bypass in n/a","id":"CVE-2006-1365","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-1366"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2006-1364"},"products":["n/a"],"published":"2006-03-23","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can bypass Bluetooth authentication to add trusted devices and gain AT level access on Motorola phones via a HeloMoto attack.","url":"https://insights.sbomify.com/CVE-2006-1365/"}