NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
34 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2024-55414 A vulnerability exits in driver SmSerl64.sys in Motorola SM56 Modem WDM Driver v6.12.23.0, which allows low-privileged users to mapping physical memory via spe… 2025-01-07 critical9.8 CVE-2024-38281 An attacker can access the maintenance console using hard coded credentials for a hidden wireless network on the device. motorola · vigilant_fixed_lpr_coms_box_firmware 2024-06-13 critical9.0 CVE-2024-23630 An arbitrary firmware upload vulnerability exists in the Motorola MR2600. motorola · mr2600_firmware 2024-01-26 critical9.6 CVE-2024-23629 An authentication bypass vulnerability exists in the web component of the Motorola MR2600. motorola · mr2600_firmware 2024-01-26 critical9.0 CVE-2024-23628 A command injection vulnerability exists in the 'SaveStaticRouteIPv6Params' parameter of the Motorola MR2600. motorola · mr2600_firmware 2024-01-26 critical9.0 CVE-2024-23627 A command injection vulnerability exists in the 'SaveStaticRouteIPv4Params' parameter of the Motorola MR2600. motorola · mr2600_firmware 2024-01-26 critical9.0 CVE-2024-23626 A command injection vulnerability exists in the ‘SaveSysLogParams’ parameter of the Motorola MR2600. motorola · mr2600_firmware 2024-01-26 critical9.6 CVE-2022-26941 A format string vulnerability exists in Motorola MTM5000 series firmware AT command handler for the AT+CTGL command. motorola · mtm5500_firmware, motorola · mtm5400_firmware 2023-10-19 critical9.4 CVE-2023-23770 Motorola MBTS Site Controller accepts hard-coded backdoor password. motorola · mbts_site_controller_firmware 2023-08-29 critical9.8 CVE-2022-30274 The Motorola ACE1000 RTU through 2022-05-02 uses ECB encryption unsafely. motorola · ace1000_firmware 2022-07-26 critical9.8 CVE-2022-30271 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 … motorola · ace1000_firmware 2022-07-26 critical9.8 CVE-2022-30270 The Motorola ACE1000 RTU through 2022-05-02 has default credentials. motorola · ace1000_firmware 2022-07-26 critical9.8 CVE-2022-30273 The Motorola MDLC protocol through 2022-05-02 mishandles message integrity. motorolasolutions · mdlc 2022-07-26 critical9.8 CVE-2020-21937 An command injection vulnerability in HNAP1/SetWLanApcliSettings of Motorola CX2 router CX 1.0.2 Build 20190508 Rel.97360n allows attackers to execute arbitrar… motorola · cx2_firmware 2021-07-21 critical9.8 CVE-2020-21935 A command injection vulnerability in HNAP1/GetNetworkTomographySettings of Motorola CX2 router CX 1.0.2 Build 20190508 Rel.97360n allows attackers to execute a… motorola · cx2_firmware 2021-07-21 critical9.8 CVE-2021-32089 An issue was discovered on Zebra (formerly Motorola Solutions) Fixed RFID Reader FX9500 devices. zebra · fx9500_firmware 2021-05-11 critical9.8 CVE-2019-16257 Some Motorola devices include the SIMalliance Toolbox Browser (aka S@T Browser) on the UICC, which might allow remote attackers to retrieve location and IMEI i… motorola · motorola_firmware 2019-09-12 critical9.8 CVE-2019-12297 An issue was discovered in scopd on Motorola routers CX2 1.01 and M2 1.01. motorola · cx2_firmware, motorola · m2_firmware 2019-05-23 critical9.8 CVE-2019-11322 An issue was discovered in Motorola CX2 1.01 and M2 1.01. motorola · cx2_firmware, motorola · m2_firmware 2019-04-18 critical9.8 CVE-2019-11320 In Motorola CX2 1.01 and M2 1.01, users can access the router's /priv_mgt.html web page to launch telnetd, as demonstrated by the 192.168.51.1 address. motorola · cx2_firmware, motorola · m2_firmware 2019-04-18 critical9.8 CVE-2019-11319 An issue was discovered in Motorola CX2 1.01 and M2 1.01. motorola · cx2_firmware, motorola · m2_firmware 2019-04-18 critical9.8 CVE-2019-9121 An issue was discovered on Motorola C1 and M2 devices with firmware 1.01 and 1.07 respectively. motorola · m2_firmware, motorola · c1_firmware 2019-03-07 critical9.8 CVE-2019-9120 An issue was discovered on Motorola C1 and M2 devices with firmware 1.01 and 1.07 respectively. motorola · m2_firmware, motorola · c1_firmware 2019-03-07 critical9.8 CVE-2019-9119 An issue was discovered on Motorola C1 and M2 devices with firmware 1.01 and 1.07 respectively. motorola · m2_firmware, motorola · c1_firmware 2019-03-07 critical9.8 CVE-2019-9118 An issue was discovered on Motorola C1 and M2 devices with firmware 1.01 and 1.07 respectively. motorola · m2_firmware, motorola · c1_firmware 2019-03-07 critical9.8 CVE-2019-9117 An issue was discovered on Motorola C1 and M2 devices with firmware 1.01 and 1.07 respectively. motorola · m2_firmware, motorola · c1_firmware 2019-03-07 critical9.8 CVE-2018-20399 Motorola SBG901 SBG901-2.10.1.1-GA-00-581-NOSH, SBG941 SBG941-2.11.0.0-GA-07-624-NOSH, and SVG1202 SVG1202-2.1.0.0-GA-14-LTSH devices allow remote attackers to… motorola · sbg901_firmware, motorola · sbg941_firmware, motorola · svg1202_firmware 2018-12-23 critical9.8 CVE-2017-0829 An elevation of privilege vulnerability in the Motorola bootloader. google · android 2017-10-04 critical9.3 CVE-2009-1394 Stack-based buffer overflow in Motorola Timbuktu Pro 8.6.5 on Windows allows remote attackers to execute arbitrary code by sending a long malformed string over… motorola · timbuktu_pro 2009-06-26 critical9.3 CVE-2008-2548 Stack-based buffer overflow in the JPEG thumbprint component in the EXIF parser on Motorola cell phones with RAZR firmware allows user-assisted remote attacker… motorola · razr 2008-06-04

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.