NetSight

Security Dashboard

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

Reset
61 matching advisories · page 2 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2020-25014 A stack-based buffer overflow in fbwifi_continue.cgi on Zyxel UTM and VPN series of gateways running firmware version V4.30 through to V4.55 allows remote unau… zyxel · zld, zyxel · access_points_firmware 2020-11-27 critical9.8 CVE-2020-24355 Zyxel VMG5313-B30B router on firmware 5.13(ABCJ.6)b3_1127, and possibly older versions of firmware are affected by insecure permissions which allows regular an… zyxel · vmg5313-b30b_firmware 2020-09-02 critical9.8 CVE-2020-15324 Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a world-readable axess/opt/axXMPPHandler/config/xmpp_config.py file that stores hardcoded credentials. zyxel · cloud_cnm_secumanager 2020-06-29 critical9.8 CVE-2020-15323 Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has the cloud1234 password for the a1@chopin account default credentials. zyxel · cloudcnm_secumanager 2020-06-29 critical9.8 CVE-2020-15322 Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has the wbboEZ4BN3ssxAfM hardcoded password for the debian-sys-maint account. zyxel · cloudcnm_secumanager 2020-06-29 critical9.8 CVE-2020-15321 Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has the axzyxel password for the livedbuser account. zyxel · cloudcnm_secumanager 2020-06-29 critical9.8 CVE-2020-15320 Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has the axiros password for the root account. zyxel · cloudcnm_secumanager 2020-06-29 critical9.8 CVE-2020-15348 Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 allows use of live/CPEManager/AXCampaignManager/delete_cpes_by_ids?cpe_ids= for eval injection of Python code. zyxel · cloud_cnm_secumanager 2020-06-26 critical9.8 CVE-2020-9054 Zyxel Multiple NAS Devices OS Command Injection VulnerabilityExploited zyxel · nas326_firmware, zyxel · nas520_firmware, zyxel · nas540_firmware +9 2020-03-04 critical9.1 CVE-2019-15803 An issue was discovered on Zyxel GS1900 devices with firmware before 2.50(AAHH.0)C0. zyxel · gs1900-8_firmware, zyxel · gs1900-8hp_firmware, zyxel · gs1900-10hp_firmware +6 2019-11-14 critical9.8 CVE-2019-15800 An issue was discovered on Zyxel GS1900 devices with firmware before 2.50(AAHH.0)C0. zyxel · gs1900-8_firmware, zyxel · gs1900-8hp_firmware, zyxel · gs1900-10hp_firmware +6 2019-11-14 critical9.4 CVE-2019-17354 wan.htm page on Zyxel NBG-418N v2 with firmware version V1.00(AARP.9)C0 can be accessed directly without authentication, which can lead to disclosure of inform… zyxel · nbg-418n_v2_firmware 2019-10-09 critical9.1 CVE-2019-12583 Missing Access Control in the "Free Time" component of several Zyxel UAG, USG, and ZyWall devices allows a remote attacker to generate guest accounts by direct… zyxel · uag2100_firmware, zyxel · uag4100_firmware, zyxel · uag5100_firmware +9 2019-06-27 critical9.8 CVE-2019-6725 The rpWLANRedirect.asp ASP page is accessible without authentication on ZyXEL P-660HN-T1 V2 (2.00(AAKK.3)) devices. zyxel · p-660hn-t1_firmware 2019-05-31 critical9.8 CVE-2017-18371 The ZyXEL P660HN-T1A v2 TCLinux Fw #7.3.37.6 router distributed by TrueOnline has three user accounts with default passwords, including two hardcoded service a… billion · 5200w-t_firmware, zyxel · p660hn-t1a_v2_firmware, zyxel · p660hn-t1a_v1_firmware 2019-05-02 critical9.8 CVE-2017-18368 Zyxel P660HN-T1A Routers Command Injection VulnerabilityExploited billion · 5200w-t_firmware, zyxel · p660hn-t1a_v2_firmware, zyxel · p660hn-t1a_v1_firmware 2019-05-02 critical9.8 CVE-2018-18754 ZyXEL VMG3312-B10B 1.00(AAPP.7) devices have a backdoor root account with the tTn3+Z@!Sr0O+ password hash in the etc/default.cfg file. zyxel · vmg3312-b10b_firmware 2018-10-29 critical9.8 CVE-2018-1164 This vulnerability allows remote attackers to cause a denial-of-service condition on vulnerable installations of ZyXEL P-870H-51 DSL Router 1.00(AWG.3)D5. zyxel · p-870h-51_firmware 2018-02-21 critical9.8 CVE-2017-15226 Zyxel NBG6716 V1.00(AAKG.9)C0 devices allow command injection in the ozkerz component because beginIndex and endIndex are used directly in a popen call. zyxel · nbg6716_firmware 2017-10-10 critical9.8 CVE-2017-3216 WiMAX routers based on the MediaTek SDK (libmtk) that use a custom httpd plugin are vulnerable to an authentication bypass allowing a remote, unauthenticated a… greenpacket · ox350_firmware, huawei · bm2022_firmware, huawei · hes-309m_firmware +9 2017-06-20 critical10.0 CVE-2017-7964 Zyxel WRE6505 devices have a default TELNET password of 1234 for the root and admin accounts, which makes it easier for remote attackers to conduct DNS hijacki… zyxel · wre6505_firmware 2017-04-19 critical9.8 CVE-2016-1329 Cisco NX-OS 6.0(2)U6(1) through 6.0(2)U6(5) on Nexus 3000 devices and 6.0(2)A6(1) through 6.0(2)A6(5) and 6.0(2)A7(1) on Nexus 3500 devices has hardcoded crede… samsung · x14j_firmware, sun · opensolaris, zyxel · gs1900-10hp_firmware +1 2016-03-03 critical9.8 CVE-2015-5989 Belkin F9K1102 2 devices with firmware 2.10.17 rely on client-side JavaScript code for authorization, which allows remote attackers to obtain administrative pr… zyxel · gs1900-10hp_firmware 2015-12-31 critical9.8 CVE-2015-5988 The web management interface on Belkin F9K1102 2 devices with firmware 2.10.17 has a blank password, which allows remote attackers to obtain administrative pri… zyxel · gs1900-10hp_firmware 2015-12-31 critical9.8 CVE-2015-6018 The diagnostic-ping implementation on ZyXEL PMG5318-B20A devices with firmware before 1.00(AANC.2)C0 allows remote attackers to execute arbitrary commands via … zyxel · pmg5318-b20a_firmware 2015-12-31 critical9.8 CVE-2015-6016 ZyXEL P-660HW-T1 2 devices with ZyNOS firmware 3.40(AXH.0), PMG5318-B20A devices with firmware 1.00AANC0b5, and NBG-418N devices have a default password of 123… zyxel · nbg-418n, zyxel · zynos_firmware, zyxel · pmg5318-b20a_firmware 2015-12-31 critical9.3 CVE-2007-6730 Multiple cross-site request forgery (CSRF) vulnerabilities in the web management interface in the ZyXEL P-330W router allow remote attackers to hijack the auth… zyxel · p-330w_router 2009-09-10 critical9.8 CVE-2008-1160 ZyXEL ZyWALL 1050 has a hard-coded password for the Quagga and Zebra processes that is not changed when it is set by a user, which allows remote attackers to g… zyxel · zywall_1050_firmware 2008-03-25 critical10.0 CVE-2008-1255 The ZyXEL P-660HW series router maintains authentication state by IP address, which allows remote attackers to bypass authentication by establishing a session … zyxel · p-660hw 2008-03-10 critical10.0 CVE-2008-1256 The ZyXEL P-660HW series router has "admin" as its default password, which allows remote attackers to gain administrative access. zyxel · p-660hw 2008-03-10

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.