Vulnerabilities (CVE)

Filtered by vendor Motorola Subscribe
Total 95 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2007-4220 1 Motorola 1 Timbuktu 2024-11-21 7.8 HIGH N/A
Directory traversal vulnerability in Motorola Timbuktu Pro before 8.6.5 for Windows allows remote attackers to create or delete arbitrary files via a .. (dot dot) in a Send request, probably related to the (1) Send and (2) Exchange services.
CVE-2007-0522 1 Motorola 1 Motorazr 2024-11-21 3.3 LOW N/A
The Motorola MOTORAZR V3 phone allows remote attackers to cause a denial of service (continual modal dialogs and UI unavailability) by repeatedly trying to OBEX push a file over Bluetooth, as demonstrated by ussp-push.
CVE-2006-5196 1 Motorola 1 Surfboard 2024-11-21 7.8 HIGH N/A
The HTTP interface in the Motorola SURFboard SB4200 Cable Modem allows remote attackers to cause a denial of service (device crash) via a request with MfcISAPICommand set to SecretProc and a long string in the Secret parameter.
CVE-2006-1367 1 Motorola 2 Pebl U6, V600 2024-11-21 6.8 MEDIUM N/A
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.
CVE-2006-1366 1 Motorola 1 Pebl U6 2024-11-21 7.8 HIGH N/A
Buffer overflow in the Motorola PEBL U6 08.83.76R, and possibly other Motorola P2K-based phones, allows remote attackers to cause a denial of service (device shutdown), and possibly execute arbitrary code, via a long OBEX setpath to the OBEX File Transfer (aka FTP) service on Bluetooth channel 9.
CVE-2006-1365 1 Motorola 3 E398, Pebl U6, V600 2024-11-21 5.0 MEDIUM N/A
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.
CVE-2005-4215 1 Motorola 1 Motorola Cable Modem 2024-11-21 7.8 HIGH N/A
Motorola SB5100E Cable Modem allows remote attackers to cause a denial of service (device crash) via an IP packet with the same source and destination IPs and ports, and with the SYN flag set (aka LAND).
CVE-2004-1550 1 Motorola 1 Wr850g 2024-11-20 7.5 HIGH N/A
Motorola Wireless Router WR850G running firmware 4.03 allows remote attackers to bypass authentication, log on as an administrator, and obtain sensitive information by repeatedly making an HTTP request for ver.asp until an administrator logs on.
CVE-2002-1944 1 Motorola 1 Surfboard 2024-11-20 5.0 MEDIUM N/A
Motorola Surfboard 4200 cable modem allows remote attackers to cause a denial of service (crash) by performing a SYN scan using a tool such as nmap.
CVE-1999-0919 1 Motorola 1 Motorola Cablerouter 2024-11-20 10.0 HIGH N/A
A memory leak in a Motorola CableRouter allows remote attackers to conduct a denial of service via a large number of telnet connections.
CVE-1999-0816 1 Motorola 1 Motorola Cablerouter 2024-11-20 10.0 HIGH N/A
The Motorola CableRouter allows any remote user to connect to and configure the router on port 1024.
CVE-2024-25360 1 Motorola 2 Cx2l, Cx2l Firmware 2024-10-30 N/A 5.3 MEDIUM
A hidden interface in Motorola CX2L Router firmware v1.0.1 leaks information regarding the SystemWizardStatus component via sending a crafted request to device_web_ip.
CVE-2024-23629 1 Motorola 2 Mr2600, Mr2600 Firmware 2024-10-18 7.8 HIGH 7.5 HIGH
An authentication bypass vulnerability exists in the web component of the Motorola MR2600. An attacker can exploit this vulnerability to access protected URLs and retrieve sensitive information.
CVE-2024-38280 1 Motorola 2 Vigilant Fixed Lpr Coms Box, Vigilant Fixed Lpr Coms Box Firmware 2024-10-03 N/A 4.6 MEDIUM
An unauthorized user is able to gain access to sensitive data, including credentials, by physically retrieving the hard disk of the product as the data is stored in clear text.
CVE-2024-38279 1 Motorola 2 Vigilant Fixed Lpr Coms Box, Vigilant Fixed Lpr Coms Box Firmware 2024-10-03 N/A 4.6 MEDIUM
The affected product is vulnerable to an attacker modifying the bootloader by using custom arguments to bypass authentication and gain access to the file system and obtain password hashes.
CVE-2024-38281 1 Motorola 2 Vigilant Fixed Lpr Coms Box, Vigilant Fixed Lpr Coms Box Firmware 2024-10-03 N/A 9.8 CRITICAL
An attacker can access the maintenance console using hard coded credentials for a hidden wireless network on the device.
CVE-2023-23774 1 Motorola 4 Ebts Site Controller, Ebts Site Controller Firmware, Mbts Site Controller and 1 more 2024-10-03 N/A 8.4 HIGH
Motorola EBTS/MBTS Site Controller drops to debug prompt on unhandled exception. The Motorola MBTS Site Controller exposes a debug prompt on the device's serial port in case of an unhandled exception. This allows an attacker with physical access that is able to trigger such an exception to extract secret key material and/or gain arbitrary code execution on the device.
CVE-2022-4002 1 Motorola 2 Q14, Q14 Firmware 2024-08-13 N/A 7.2 HIGH
A command injection vulnerability could allow an authenticated user to execute operating system commands as root via a specially crafted API request.
CVE-2022-4003 1 Motorola 2 Q14, Q14 Firmware 2024-08-13 N/A 6.5 MEDIUM
A denial-of-service vulnerability could allow an authenticated user to trigger an internal service restart via a specially crafted API request.
CVE-2022-30271 1 Motorola 2 Ace1000, Ace1000 Firmware 2024-08-01 N/A 9.8 CRITICAL
The Motorola ACE1000 RTU through 2022-05-02 ships with a hardcoded SSH private key and initialization scripts (such as /etc/init.d/sshd_service) only generate a new key if no private-key file exists. Thus, this hardcoded key is likely to be used by default.