{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1367 exists.","fix":"No fix has been published for CVE-2006-1367 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-1367 is a medium-severity vulnerability in n/a, published on 23 Mar 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2006-1367 and fix it if it is affected.\n\nWhat it is: CVE-2006-1367 is a medium-severity vulnerability in n/a, published on 23 Mar 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1367 exists.\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-1367/ (Markdown: https://insights.sbomify.com/CVE-2006-1367/index.md)","id":"CVE-2006-1367","markdown":"https://insights.sbomify.com/CVE-2006-1367/index.md","name":"CVE-2006-1367","record":{"aliases":["GHSA-mq67-c8r3-w2f5"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Motorola P2K phones","requires_auth":"none","summary":"Attackers can view phonebook and SMS data on Motorola P2K phones via Bluetooth by tricking users into granting access due to GUI misrepresentation.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pebl_u6","vendor":"motorola"},{"product":"v600","vendor":"motorola"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Motorola PEBL U6 08.83.76R, the Motorola V600, and possibly the Motorola E398 and other Motorola P2K-based phones does not require pairing for a connection related to the Headset Audio Gateway service, which allows user-assisted remote attackers to obtain AT level access and view phonebook entries and saved SMS messages by connecting on Bluetooth channel 3 and tricking the user into pressing Grant, aka a \"Blueline\" attack.  NOTE: while user-assisted, the attack is made more feasible because of a GUI misrepresentation issue that allows a default message to be replaced by an attacker-specified one.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-03-22","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-03-22","kind":"exploitdb","ref":"27454","stars":null,"title":"Motorola - BlueTooth Interface Dialog Spoofing"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2006-1367","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":7,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-1368"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2006-1366"},"products":["n/a"],"published":"2006-03-23","related":[{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2006-1366","kev_date_added":null,"published":"2006-03-23"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Attackers can view phonebook and SMS data on Motorola P2K phones via Bluetooth by tricking users into granting access due to GUI misrepresentation.","url":"https://insights.sbomify.com/CVE-2006-1367/"}