NetSight

Security Dashboard

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

Reset
141 matching advisories · page 2 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.0 CVE-2023-41816 An improper export vulnerability was reported in the Motorola Services Main application that could allow a local attacker to write to a local database. 2024-05-03 medium5.0 CVE-2023-41829 An improper export vulnerability was reported in the Motorola Carrier Services application that could allow a malicious, local application to read files withou… 2024-03-04 medium5.1 CVE-2023-41827 An improper export vulnerability was reported in the Motorola OTA update application, that could allow a malicious, local application to inject an HTML-based m… 2024-03-04 medium5.3 CVE-2024-25360 A hidden interface in Motorola CX2L Router firmware v1.0.1 leaks information regarding the SystemWizardStatus component via sending a crafted request to device… motorola · cx2l_firmware 2024-02-12 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 medium6.5 CVE-2022-3681 A vulnerability has been identified in the MR2600 router v1.0.18 and earlier that could allow an attacker within range of the wireless network to successfully … motorola · mr2600 2023-10-27 high8.1 CVE-2022-27813 Motorola MTM5000 series firmwares lack properly configured memory protection of pages shared between the OMAP-L138 ARM and DSP cores. motorola · mtm5500_firmware, motorola · mtm5400_firmware 2023-10-19 high8.8 CVE-2022-26943 The Motorola MTM5000 series firmwares generate TETRA authentication challenges using a PRNG using a tick count register as its sole entropy source. motorola · mtm5500_firmware, motorola · mtm5400_firmware 2023-10-19 high8.2 CVE-2022-26942 The Motorola MTM5000 series firmwares lack pointer validation on arguments passed to trusted execution environment (TEE) modules. motorola · mtm5500_firmware, motorola · mtm5400_firmware 2023-10-19 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 medium4.9 CVE-2022-3407 I some cases, when the device is USB-tethered to a host PC, and the device is sharing its mobile network connection with the host PC, if the user originates a … motorola · smartphone_firmware 2023-09-01 high8.4 CVE-2023-23774 Motorola EBTS/MBTS Site Controller drops to debug prompt on unhandled exception. motorola · ebts_site_controller_firmware, motorola · mbts_site_controller_firmware 2023-08-29 high7.2 CVE-2023-23773 Motorola EBTS/MBTS Base Radio fails to check firmware authenticity. motorola · ebts_base_radio_firmware, motorola · mbts_base_radio_firmware 2023-08-29 high7.2 CVE-2023-23772 Motorola MBTS Site Controller fails to check firmware update authenticity. motorola · mbts_site_controller_firmware 2023-08-29 high8.4 CVE-2023-23771 Motorola MBTS Base Radio accepts hard-coded backdoor password. motorola · mbts_base_radio_firmware 2023-08-29 critical9.4 CVE-2023-23770 Motorola MBTS Site Controller accepts hard-coded backdoor password. motorola · mbts_site_controller_firmware 2023-08-29 high8.8 CVE-2023-31531 Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the tomography_ping_number parameter. motorola · cx2l_firmware 2023-05-11 high8.8 CVE-2023-31530 Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the smartqos_priority_devices parameter. motorola · cx2l_firmware 2023-05-11 high8.8 CVE-2023-31529 Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the system_time_timezone parameter. motorola · cx2l_firmware 2023-05-11 high8.8 CVE-2023-31528 Motorola CX2L Router 1.0.1 was discovered to contain a command injection vulnerability via the staticroute_list parameter. motorola · cx2l_firmware 2023-05-11 high7.2 CVE-2022-34885 An improper input sanitization vulnerability in the Motorola MR2600 router could allow a local user with elevated permissions to execute arbitrary code. motorola · mr2600_firmware 2023-01-30 medium4.6 CVE-2022-3917 Improper access control of bootloader function was discovered in Motorola Mobility Motorola e20 prior to version RONS31.267-38-8 allows attacker with local acc… motorola · moto_e20_firmware 2022-12-14 high7.5 CVE-2022-30276 The Motorola MOSCAD and ACE line of RTUs through 2022-05-02 omit an authentication requirement. motorola · moscad_ip_gateway_firmware, motorola · ace_ip_gateway_\(4600\)_firmware 2022-07-26 critical9.8 CVE-2022-30274 The Motorola ACE1000 RTU through 2022-05-02 uses ECB encryption unsafely. motorola · ace1000_firmware 2022-07-26 high7.2 CVE-2022-30272 The Motorola ACE1000 RTU through 2022-05-02 mishandles firmware integrity. 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

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.