NetSight

Security Dashboard

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

Reset
305 matching advisories · page 8 of 11Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2020-9255 Huawei Honor 10 smartphones with versions earlier than 10.0.0.178(C00E178R1P4) have a denial of service vulnerability. huawei · honor_10_firmware 2020-07-17 high7.1 CVE-2020-14152 In IJG JPEG (aka libjpeg) before 9d, jpeg_mem_available() in jmemnobs.c in djpeg does not honor the max_memory_to_use setting, possibly causing excessive memor… ijg · libjpeg, debian · debian_linux 2020-06-15 medium4.3 CVE-2020-10754 It was found that nmcli, a command line interface to NetworkManager did not honour 802-1x.ca-path and 802-1x.phase2-ca-path settings, when creating a new profi… gnome · networkmanager, fedoraproject · fedora 2020-06-08 medium5.3 CVE-2020-9074 Huawei Smartphones HONOR 20 PRO;Honor View 20;HONOR 20 have an improper handling of exceptional condition Vulnerability. huawei · honor_20_pro_firmware, huawei · honor_view_20_firmware, huawei · honor_20_firmware 2020-06-05 low2.4 CVE-2020-1833 Honor 9X smartphones with versions earlier than 9.1.1.172(C00E170R8P1) have an improper authentication vulnerability. huawei · honor_9x_firmware 2020-05-29 medium6.5 CVE-2020-9069 There is an information leakage vulnerability in some Huawei products. huawei · anne-al00_firmware, huawei · berkeley-l09_firmware, huawei · cd16-10_firmware +9 2020-05-21 high7.1 CVE-2020-1808 Honor 20;HONOR 20 PRO;Honor Magic2;HUAWEI Mate 20 X;HUAWEI P30;HUAWEI P30 Pro;Honor View 20 smartphones with versions earlier than 10.0.0.187(C00E60R4P11); ver… huawei · honor_view_20_firmware, huawei · honor_20_firmware, huawei · honor_20_pro_firmware +1 2020-05-15 high7.1 CVE-2020-1806 Huawei Honor V10 smartphones with versions earlier than 10.0.0.156(C00E156R2P4) has three out of bounds vulnerabilities. huawei · honor_v10_firmware 2020-04-27 high7.1 CVE-2020-1805 Huawei Honor V10 smartphones with versions earlier than 10.0.0.156(C00E156R2P4) has three out of bounds vulnerabilities. huawei · honor_v10_firmware 2020-04-27 high7.1 CVE-2020-1804 Huawei Honor V10 smartphones with versions earlier than 10.0.0.156(C00E156R2P4) has three out of bounds vulnerabilities. huawei · honor_v10_firmware 2020-04-27 medium5.3 CVE-2020-1803 Huawei smartphones Honor V20 with versions earlier than 10.0.0.179(C636E3R4P3),versions earlier than 10.0.0.180(C185E3R3P3),versions earlier than 10.0.0.180(C4… huawei · honor_v20_firmware 2020-04-20 critical9.1 CVE-2019-14887 A flaw was found when an OpenSSL security provider is used with Wildfly, the 'enabled-protocols' value in the Wildfly configuration isn't honored. redhat · jboss_data_grid, redhat · jboss_enterprise_application_platform, redhat · jboss_fuse +3 2020-03-16 medium5.5 CVE-2020-9064 Huawei smartphone Honor V30 with versions earlier than OxfordS-AN00A 10.0.1.167(C00E166R4P1) have an improper authentication vulnerability. huawei · honor_v30_firmware 2020-03-12 high7.8 CVE-2020-0069 Mediatek Multiple Chipsets Insufficient Input Validation VulnerabilityExploited google · android, huawei · berkeley-l09_firmware, huawei · columbia-al10b_firmware +9 2020-03-10 medium5.5 CVE-2020-1792 Honor V10 smartphones with versions earlier than BKL-AL20 10.0.0.156(C00E156R2P4) and versions earlier than BKL-L09 10.0.0.146(C432E4R1P4) have an out of bound… huawei · honor_v10_firmware 2020-02-28 medium4.6 CVE-2020-1882 Huawei mobile phones Ever-L29B versions earlier than 10.0.0.180(C185E6R3P3), earlier than 10.0.0.180(C432E6R1P7), earlier than 10.0.0.180(C636E5R2P3); HUAWEI M… huawei · mate_20_rs_firmware, huawei · mate_20_x_firmware, huawei · honor_magic2_firmware +1 2020-02-18 medium5.5 CVE-2020-1788 Honor V30 smartphones with versions earlier than 10.0.1.135(C00E130R4P1) have an improper authentication vulnerability. huawei · honor_v30_firmware 2020-01-21 medium4.4 CVE-2020-1826 Huawei Honor Magic2 mobile phones with versions earlier than 10.0.0.175(C00E59R2P11) have an information leak vulnerability. huawei · honor_magic2_firmware 2020-01-09 medium5.5 CVE-2020-1785 Mate 10 Pro;Honor V10;Honor 10;Nova 4 smartphones have a denial of service vulnerability. huawei · mate_10_pro_firmware, huawei · honor_v10_firmware, huawei · honor_10_firmware +1 2020-01-03 critical9.8 CVE-2012-6094 cups (Common Unix Printing System) 'Listen localhost:631' option not honored correctly which could provide unauthorized access to the system apple · cups, debian · debian_linux 2019-12-20 low3.5 CVE-2019-5252 There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). huawei · enjoy_8_plus_firmware, huawei · y9_firmware, huawei · honor_8x_firmware +3 2019-12-14 medium4.6 CVE-2019-5264 There is an information disclosure vulnerability in certain Huawei smartphones (Mate 10;Mate 10 Pro;Honor V10;Changxiang 7S;P-smart;Changxiang 8 Plus;Y9 2018;H… huawei · mate_10_firmware, huawei · mate_10_pro_firmware, huawei · honor_v10_firmware +7 2019-12-13 medium6.5 CVE-2019-5260 Huawei smartphones HUAWEI Y9 2019 and Honor View 20 have a denial of service vulnerability. huawei · y9_2019_firmware, huawei · view_20_firmware 2019-12-13 medium5.5 CVE-2019-5251 There is a path traversal vulnerability in several Huawei smartphones. huawei · honor_v10_firmware, huawei · p30_firmware, huawei · enjoy_7s_firmware +6 2019-12-13 medium4.6 CVE-2019-5309 Honor play smartphones with versions earlier than 9.1.0.333(C00E333R1P1T8) have an information disclosure vulnerability in certain Huawei . huawei · honor_play_firmware 2019-11-29 high8.8 CVE-2019-5218 There is an insufficient authentication vulnerability in Huawei Band 2 and Honor Band 3. huawei · band_2_firmware, huawei · band_3_firmware 2019-11-29 high7.5 CVE-2019-18949 SnowHaze before 2.6.6 is sometimes too late to honor a per-site JavaScript blocking setting, which leads to unintended JavaScript execution via a chain of webp… snowhaze · snowhaze 2019-11-14 low3.3 CVE-2019-5292 Honor 10 Lite, Honor 8A, Huawei Y6 mobile phones with the versions before 9.1.0.217(C00E215R3P1), the versions before 9.1.0.205(C00E97R1P9), the versions befor… huawei · honor_10_lite_firmware, huawei · honor_8a_firmware, huawei · huawei_y6_firmware 2019-11-13 high7.8 CVE-2019-5228 Certain detection module of P30, P30 Pro, Honor V20 smartphone whith Versions earlier than ELLE-AL00B 9.1.0.193(C00E190R1P21), Versions earlier than VOGUE-AL00… huawei · p30_firmware, huawei · p30_pro_firmware, huawei · honor_v20_firmware 2019-11-12 low2.4 CVE-2019-5213 Honor play smartphones with versions earlier than Cornell-AL00A 9.1.0.321(C00E320R1P1T8) have an insufficient authentication vulnerability. huawei · honor_play_firmware 2019-11-12

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.