CVE-2006-1365: n/a vulnerability

CVE-2006-1365: The Motorola PEBL U6, the Motorola V600, and possibly the Motorola E398 and other Motorola phones allow rem...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 17:12 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2006-1365 affects legacy Motorola phones. A nearby Bluetooth attacker could reportedly get their device added to the phone’s trusted Bluetooth device list during an interrupted OBEX vCard transfer, possibly enabling deeper phone control. This is mainly a legacy-device exposure issue, not a modern enterprise software issue. Exposure is likely limited to organizations still using or storing operational affected Motorola Bluetooth phones. Risk requires Bluetooth proximity and an affected handset with vulnerable Bluetooth behavior. Modern smartphones and unrelated Motorola products are not identified as affected in the provided sources. Low business urgency unless affected legacy Motorola phones remain in operational use. If they do, prioritize retirement or isolation because the sources do not identify a reliable patch and the issue could undermine Bluetooth trust boundaries. Mitigation focus: Inventory for Motorola PEBL U6, V600, E398, and similar legacy Motorola phones.; Check Motorola or carrier guidance for any model-specific updates or retirement advice.; Disable Bluetooth where those phones are still retained for business use..

Prepared: Jun 29, 2026, 13:35 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2006-1365 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Mar 23, 2006, 23:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.