NetSight

Security Dashboard

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

Reset
79 matching advisories · page 2 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2021-21750 ZTE BigVideo Analysis product has a privilege escalation vulnerability. zte · zxin10_cms 2021-12-27 high7.5 CVE-2021-21744 ZTE MF971R product has a configuration file control vulnerability. zte · mf971r_firmware 2021-10-20 high7.5 CVE-2021-21737 A smart STB product of ZTE is impacted by a permission and access control vulnerability. zte · zxv10_b860h_v5.0_firmware 2021-06-24 high7.2 CVE-2021-21736 A smart camera product of ZTE is impacted by a permission and access control vulnerability. zte · zxhn_hs562_firmware 2021-06-10 high7.5 CVE-2021-21732 A mobile phone of ZTE is impacted by improper access control vulnerability. zte · axon_11_5g_firmware 2021-05-19 high8.1 CVE-2021-21731 A CSRF vulnerability exists in the management page of a ZTE product.The vulnerability is caused because the management page does not fully verify whether the r… zte · zxcloud_irai 2021-04-13 high7.5 CVE-2021-21727 A ZTE product has a DoS vulnerability. zte · zxhn_f623_firmware 2021-03-29 high7.5 CVE-2021-21723 Some ZTE products have a DoS vulnerability. zte · zxr10_9904_firmware, zte · zxr10_9908_firmware, zte · zxr10_9916_firmware +2 2021-01-26 high7.5 CVE-2020-6882 ZTE E8810/E8820/E8822 series routers have an information leak vulnerability, which is caused by hard-coded MQTT service access credentials on the device. zte · zxhn_e8810_firmware, zte · zxhn_e8820_firmware, zte · zxhn_e8822_firmware 2020-12-21 high7.5 CVE-2020-6881 ZTE E8810/E8820/E8822 series routers have an MQTT DoS vulnerability, which is caused by the failure of the device to verify the validity of abnormal messages. zte · zxhn_e8810_firmware, zte · zxhn_e8820_firmware, zte · zxhn_e8822_firmware 2020-12-21 high8.8 CVE-2020-6877 A ZTE product is impacted by an information leak vulnerability. zte · zxa10_eodn_firmware 2020-11-05 high8.0 CVE-2020-6870 The version V12.17.20T115 of ZTE U31R20 product is impacted by a design error vulnerability. zte · netnumen_u31_r10_firmware 2020-06-24 high8.1 CVE-2020-6869 All versions up to 10.06 of ZTEMarket APK are impacted by an information leak vulnerability. zte · ztemarket_apk 2020-06-17 high7.5 CVE-2014-4019 ZTE ZXV10 W300 router with firmware W300V1.0.0a_ZRD_LK stores sensitive information under the web root with insufficient access control, which allows remote at… zte · zxv10_w300_firmware 2020-02-20 high7.2 CVE-2019-3427 The version V6.01.03.01 of ZTE ZXCDN IAMWEB product is impacted by a code injection vulnerability. zte · zxcdn_iamweb_firmware 2019-11-22 high8.2 CVE-2019-3424 authentication issues vulnerability, which exists in V2.1.14 and below versions of C520V21 smart camera devices. ztehome · c520v21_firmware 2019-11-18 high8.8 CVE-2019-3426 The 9000EV5.0R1B12 version, and all earlier versions of ZTE product ZXUPN-9000E are impacted by the input validation vulnerability. zte · zxupn-9000e_firmware 2019-11-08 high8.8 CVE-2019-3425 The 9000EV5.0R1B12 version, and all earlier versions of ZTE product ZXUPN-9000E are impacted by vulnerability of permission and access control. zte · zxupn-9000e_firmware 2019-11-08 high8.0 CVE-2019-3421 The 7520V3V1.0.0B09P27 version, and all earlier versions of ZTE product ZX297520V3 are impacted by a Command Injection vulnerability. ztw · zx297520v3_firmware 2019-10-31 high8.8 CVE-2019-3417 All versions up to V1.1.10P3T18 of ZTE ZXHN F670 product are impacted by command injection vulnerability. zte · zxhn_f670_firmware 2019-08-15 high7.5 CVE-2019-3411 All versions up to BD_R218V2.4 of ZTE MF920 product are impacted by information leak vulnerability. zte · mf920_firmware 2019-06-11 high7.5 CVE-2018-14990 The Coolpad Defiant device with a build fingerprint of Coolpad/cp3632a/cp3632a:7.1.1/NMF26F/099480857:user/release-keys, the ZTE ZMAX Pro with a build fingerpr… coolpad · defiant_firmware, t-mobile · revvl_plus_firmware, t-mobile · zte_zmax_pro_firmware 2019-04-25 high7.1 CVE-2018-15005 The ZTE ZMAX Champ Android device with a build fingerprint of ZTE/Z917VL/fortune:6.0.1/MMB29M/20170327.120922:user/release-keys contains a pre-installed platfo… zteusa · zte_zmax_champ_firmware 2018-12-28 high7.5 CVE-2018-7362 All versions up to V1.1.10P3T18 of ZTE ZXHN F670 product are impacted by improper access control vulnerability, which may allows an unauthorized user to perfor… zte · zxhn_f670_firmware 2018-11-16 high7.5 CVE-2017-10937 SQL injection vulnerability in all versions prior to V2.01.05.09 of the ZTE ZXIPTV-UCM product allows remote attackers to execute arbitrary SQL commands via th… zte · zxiptv-ucm_firmware 2018-07-25 high7.5 CVE-2017-10936 SQL injection vulnerability in all versions prior to V4.01.01 of the ZTE ZXCDN-SNS product allows remote attackers to execute arbitrary SQL commands via the ao… zte · zxcdn-sns_firmware 2018-07-25 high7.2 CVE-2017-10935 All versions prior to ZSRV2 V3.00.40 of the ZTE ZXR10 1800-2S products allow remote authenticated users to bypass the original password authentication protecti… zte · zxr10_1800-2s_firmware 2018-07-25 high8.8 CVE-2018-13340 Gleez CMS 1.2.0 has CSRF, as demonstrated by a /page/add request. gleeztech · gleez_cms 2018-07-05 high7.5 CVE-2014-6435 cgi-bin/AZ_Retrain.cgi in Aztech ADSL DSL5018EN (1T1R), DSL705E, and DSL705EU devices does not check for authentication, which allows remote attackers to cause… aztech · adsl_dsl5018en_\(1t1r\)_firmware, aztech · dsl705e_firmware, aztech · dsl705eu_firmware 2018-01-12 high7.5 CVE-2017-16953 connoppp.cgi on ZTE ZXDSL 831CII devices does not require HTTP Basic Authentication, which allows remote attackers to modify the PPPoE configuration or set up … zte · zxdsl_831cii_firmware 2017-12-01

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.