NetSight

Security Dashboard

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

Reset
559 matching advisories · page 15 of 19Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2017-18322 Cryptographic key material leaked in WCDMA debug messages in snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MD… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9615_firmware +9 2019-01-03 medium5.5 CVE-2017-18321 Security keys used by the terminal and NW for a session could be leaked in snapdragon mobile in versions MDM9650, MDM9655, SD 835, SDA660. qualcomm · mdm9650_firmware, qualcomm · mdm9655_firmware, qualcomm · sd_835_firmware +1 2019-01-03 medium5.5 CVE-2017-18319 Information leak in UIM API debug messages in snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9645, MDM9650,… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9615_firmware +9 2019-01-03 medium5.5 CVE-2017-11004 A non-secure user may be able to access certain registers in snapdragon automobile, snapdragon mobile and snapdragon wear in versions IPQ8074, MDM9206, MDM9607… qualcomm · ipq8074_firmware, qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware +9 2019-01-03 medium6.5 CVE-2018-5916 Buffer overread while decoding PDP modify request or network initiated secondary PDP activation in Snapdragon Automobile, Snapdragon Mobile and Snapdragon Wear… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9615_firmware +9 2018-11-28 medium5.5 CVE-2018-11951 Improper access control in core module lead XBL_LOADER performs the ZI region clear for QTEE instead of XBL_SEC in Snapdragon Mobile in version SD 845, SD 850. qualcomm · sd_845_firmware, qualcomm · sd_850_firmware 2018-10-26 medium4.7 CVE-2018-11846 The use of a non-time-constant memory comparison operation can lead to timing/side channel attacks in Snapdragon Mobile in version SD 210/SD 212/SD 205, SD 845… qualcomm · sd_210_firmware, qualcomm · sd_212_firmware, qualcomm · sd_205_firmware +2 2018-10-26 medium5.3 CVE-2017-18313 Under certain mode of operations, HLOS may be able get direct or indirect access through DXE channels to tamper with the authenticated WCNSS firmware stored in… qualcomm · msm8909w_firmware, qualcomm · sd_210_firmware, qualcomm · sd_212_firmware +7 2018-10-23 medium5.5 CVE-2017-18300 Secure display content could be accessed by third party trusted application after creating a fault in other trusted applications in Snapdragon Mobile, Snapdrag… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +5 2018-10-23 medium5.5 CVE-2017-18299 Improper translation table consolidation logic leads to resource exhaustion and QSEE error in Snapdragon Automobile, Snapdragon Mobile and Snapdragon Wear in v… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2018-10-23 medium5.5 CVE-2017-18292 Secure app running in non secure space can restart TZ by calling Widevine app API repeatedly in Snapdragon Automobile, Snapdragon Mobile and Snapdragon Wear in… qualcomm · msm8909w_firmware, qualcomm · msm8996au_firmware, qualcomm · sd_210_firmware +9 2018-10-23 medium6.5 CVE-2017-18283 Possible memory corruption when Read Val Blob Req is received with invalid parameters in Snapdragon Mobile in version QCA9379, SD 210/SD 212/SD 205, SD 625, SD… qualcomm · qca9379_firmware, qualcomm · sd_210_firmware, qualcomm · sd_212_firmware +6 2018-10-23 medium5.5 CVE-2017-18277 When dynamic memory allocation fails, currently the process sleeps for one second and continues with infinite loop without retrying for memory allocation in Sn… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9640_firmware +9 2018-10-23 medium6.5 CVE-2018-5871 In Snapdragon (Automobile, Mobile, Wear) in version MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCA6574AU, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD … qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9640_firmware +9 2018-09-20 medium4.7 CVE-2017-18302 In Snapdragon (Automobile ,Mobile) in version MSM8996AU, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SDA660, SDM429, SD… qualcomm · msm8996au_firmware, qualcomm · sd425_firmware, qualcomm · sd427_firmware +9 2018-09-20 medium5.5 CVE-2017-18301 In Small Cell SoC and Snapdragon (Automobile, Mobile, Wear) in version FSM9055, FSM9955, MDM9607, MDM9640, MDM9650, MSM8909W, SD 425, SD 427, SD 430, SD 435, S… qualcomm · fsm9055_firmware, qualcomm · fsm9955_firmware, qualcomm · mdm9607_firmware +9 2018-09-20 medium6.5 CVE-2018-5894 Improper Validation of Array Index in Multimedia While parsing an mp4 file in Snapdragon Automobile, Snapdragon Mobile and Snapdragon Wear, an out-of-bounds ac… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2018-07-06 medium4.3 CVE-2018-0249 A vulnerability when handling incoming 802.11 Association Requests for Cisco Aironet 1800 Series Access Point (APs) on Qualcomm Atheros (QCA) based hardware pl… cisco · aironet_access_point_software 2018-05-02 medium6.8 CVE-2016-10443 In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9607, MDM963… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9635m_firmware +9 2018-04-18 medium5.5 CVE-2016-10420 In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205,… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2018-04-18 medium5.5 CVE-2015-9218 In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/1… qualcomm · msm8909w_firmware, qualcomm · sd_210_firmware, qualcomm · sd_212_firmware +9 2018-04-18 medium5.3 CVE-2017-0751 An elevation of privilege vulnerability in the Qualcomm QCE driver. google · android 2018-04-05 medium5.3 CVE-2017-0748 An information disclosure vulnerability in the Qualcomm audio driver. google · android 2018-04-05 medium5.5 CVE-2016-10234 An information disclosure vulnerability in the Qualcomm IPA driver. google · android 2018-04-04 medium5.9 CVE-2018-5826 In Qualcomm Android for MSM, Firefox OS for MSM, and QRD Android with all Android releases from CAF using the Linux kernel before security patch level 2018-04-… google · android 2018-04-03 medium5.3 CVE-2017-15853 In Qualcomm Android for MSM, Firefox OS for MSM, and QRD Android with all Android releases from CAF using the Linux kernel before security patch level 2018-04-… google · android 2018-04-03 medium5.3 CVE-2017-15837 In Qualcomm Android for MSM, Firefox OS for MSM, and QRD Android with all Android releases from CAF using the Linux kernel before security patch level 2018-04-… google · android 2018-04-03 medium6.5 CVE-2017-9681 In Android before 2017-08-05 on Qualcomm MSM, Firefox OS for MSM, QRD Android, and all Android releases from CAF using the Linux kernel, if kernel memory addre… google · android 2018-03-30 medium4.7 CVE-2017-9676 In all Qualcomm products with Android releases from CAF using the Linux kernel, potential use after free scenarios and race conditions can occur when accessing… google · android 2017-09-21 medium4.7 CVE-2017-8281 In all Qualcomm products with Android releases from CAF using the Linux kernel, a race condition can allow access to already freed memory while querying event … google · android 2017-09-21

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.