NetSight

Security Dashboard

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

Reset
69 matching advisories · page 2 of 3Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2021-39278 Certain MOXA devices allow reflected XSS via the Config Import menu. moxa · wac-2004_firmware, moxa · wac-1001_firmware, moxa · wac-1001-t_firmware +9 2021-09-07 medium5.9 CVE-2020-27184 The NPort IA5000A Series devices use Telnet as one of the network device management services. moxa · nport_ia5150a_firmware, moxa · nport_ia5250a_firmware, moxa · nport_ia5450a_firmware 2021-05-14 medium6.5 CVE-2020-27149 By exploiting a vulnerability in NPort IA5150A/IA5250A Series before version 1.5, a user with “Read Only” privilege level can send requests via the web console… moxa · nport_ia5150a_firmware, moxa · nport_ia5250a_firmware, moxa · nport_ia5450a_firmware 2021-05-14 medium5.3 CVE-2020-25192 The built-in WEB server for MOXA NPort IAW5000A-I/O firmware version 2.1 or lower allows sensitive information to be displayed without proper authorization. moxa · nport_iaw5000a-i\/o_firmware 2020-12-23 medium5.3 CVE-2020-12117 Moxa Service in Moxa NPort 5150A firmware version 1.5 and earlier allows attackers to obtain sensitive configuration values via a crafted packet to UDP port 48… moxa · nport_5100a_firmware 2020-05-01 medium6.5 CVE-2020-6999 In Moxa EDS-G516E Series firmware, Version 5.2 or lower, some of the parameters in the setting pages do not ensure text is the correct size for its buffer. moxa · mds-g516e_firmware 2020-03-26 medium5.3 CVE-2019-9103 An issue was discovered on Moxa MGate MB3170 and MB3270 devices before 4.1, MB3280 and MB3480 devices before 3.1, MB3660 devices before 2.3, and MB3180 devices… moxa · mb3170_firmware, moxa · mb3270_firmware, moxa · mb3180_firmware +3 2020-03-11 medium5.3 CVE-2019-9097 An issue was discovered on Moxa MGate MB3170 and MB3270 devices before 4.1, MB3280 and MB3480 devices before 3.1, MB3660 devices before 2.3, and MB3180 devices… moxa · mb3170_firmware, moxa · mb3270_firmware, moxa · mb3180_firmware +3 2020-03-11 medium4.3 CVE-2019-10963 Moxa EDR 810, all versions 5.1 and prior, allows an unauthenticated attacker to be able to retrieve some log files from the device, which may allow sensitive i… moxa · edr-810_firmware 2019-10-08 medium6.1 CVE-2018-10700 An issue was discovered on Moxa AWK-3121 1.19 devices. moxa · awk-3121_firmware 2019-06-07 medium6.1 CVE-2018-10692 An issue was discovered on Moxa AWK-3121 1.14 devices. moxa · awk-3121_firmware 2019-06-07 medium6.1 CVE-2016-5819 Moxa G3100V2 Series, editions prior to Version 2.8, and OnCell G3111/G3151/G3211/G3251 Series, editions prior to Version 1.7 allows a reflected cross-site scri… moxa · oncell_g3100v2_firmware, moxa · oncell_g3111_firmware, moxa · oncell_g3151_firmware +2 2019-03-21 medium6.1 CVE-2019-6565 Moxa IKS and EDS fails to properly validate user input, giving unauthenticated and authenticated attackers the ability to perform XSS attacks, which may be use… moxa · iks-g6824a_firmware, moxa · eds-405a_firmware, moxa · eds-408a_firmware +1 2019-03-05 medium6.5 CVE-2019-6559 Moxa IKS and EDS allow remote authenticated users to cause a denial of service via a specially crafted packet, which may cause the switch to crash. moxa · iks-g6824a_firmware, moxa · eds-405a_firmware, moxa · eds-408a_firmware +1 2019-03-05 medium4.4 CVE-2017-12127 A password storage vulnerability exists in the operating system functionality of Moxa EDR-810 V4.1 build 17030317. moxa · edr-810_firmware 2018-05-14 medium6.5 CVE-2017-12124 An exploitable denial of service vulnerability exists in the web server functionality of Moxa EDR-810 V4.1 build 17030317. moxa · edr-810_firmware 2018-05-14 medium6.5 CVE-2018-5449 A NULL Pointer Dereference issue was discovered in Moxa OnCell G3100-HSPA Series version 1.4 Build 16062919 and prior. moxa · oncell_g3150-hspa-t_firmware, moxa · oncell_g3110-hspa-t_firmware, moxa · oncell_g3150-hspa_firmware +1 2018-03-05 medium5.3 CVE-2017-13702 An issue was discovered on MOXA EDS-G512E 5.1 build 16072215 devices. moxa · eds-g512e_firmware 2017-11-17 medium4.8 CVE-2017-13700 An issue was discovered on MOXA EDS-G512E 5.1 build 16072215 devices. moxa · eds-g512e_firmware 2017-11-17 medium5.0 CVE-2017-7457 XML External Entity via ".AOP" files used by Moxa MX-AOPC Server 1.5 result in remote file disclosure. moxa · mx-aopc_server 2017-04-14 medium5.3 CVE-2016-8725 An exploitable information disclosure vulnerability exists in the Web Application functionality of the Moxa AWK-3131A wireless access point running firmware 1.… moxa · awk-3131a_firmware 2017-04-13 medium5.3 CVE-2016-8724 An exploitable information disclosure vulnerability exists in the serviceAgent functionality of Moxa AWK-3131A Wireless Access Point running firmware 1.1. moxa · awk-3131a_firmware 2017-04-13 medium5.3 CVE-2016-8722 An exploitable Information Disclosure vulnerability exists in the Web Application functionality of Moxa AWK-3131A Series Industrial IEEE 802.11a/b/g/n wireless… moxa · awk-3131a_firmware 2017-04-13 medium4.3 CVE-2016-8720 An exploitable HTTP Header Injection vulnerability exists in the Web Application functionality of the Moxa AWK-3131A Wireless Access Point running firmware 1.1. moxa · awk-3131a_firmware 2017-04-13 medium6.1 CVE-2016-8719 An exploitable reflected Cross-Site Scripting vulnerability exists in the Web Application functionality of Moxa AWK-3131A Wireless Access Point running firmwar… moxa · awk-3131a_firmware 2017-04-12 medium6.1 CVE-2016-9371 An issue was discovered in Moxa NPort 5110 versions prior to 2.6, NPort 5130/5150 Series versions prior to 3.6, NPort 5200 Series versions prior to 2.8, NPort … moxa · nport_5100_series_firmware, moxa · nport_5200_series_firmware, moxa · nport_5400_series_firmware +7 2017-02-13 medium5.5 CVE-2016-9354 An issue was discovered in Moxa DACenter Versions 1.4 and older. moxa · dacenter 2017-02-13 medium5.3 CVE-2016-9346 An issue was discovered in Moxa MiiNePort E1 versions prior to 1.8, E2 versions prior to 1.4, and E3 versions prior to 1.1. moxa · miineport_e1_firmware, moxa · miineport_e2_firmware, moxa · miineport_e3_firmware 2017-02-13 medium6.5 CVE-2016-8362 An issue was discovered in Moxa OnCell OnCellG3470A-LTE, AWK-1131A/3131A/4131A Series, AWK-3191 Series, AWK-5232/6232 Series, AWK-1121/1127 Series, WAC-1001 V2… moxa · oncellg3470a-lte_firmware, moxa · awk-4131a_firmware, moxa · awk-3191_firmware +9 2017-02-13 medium6.1 CVE-2016-8359 An issue was discovered in Moxa ioLogik E1210, firmware Version V2.4 and prior, ioLogik E1211, firmware Version V2.3 and prior, ioLogik E1212, firmware Version… moxa · iologik_e1200_series_firmware, moxa · iologik_e2200_series_firmware 2017-02-13

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.