NetSight

Security Dashboard

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

Reset
559 matching advisories · page 13 of 19Index is being built · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2019-20775 An issue was discovered on LG mobile devices with Android OS 9.0 (Qualcomm SDM450, SDM845, SM6150, and SM8150 chipsets) software. google · android 2020-04-17 medium5.5 CVE-2019-14075 Null pointer dereference issue in radio interface layer due to lack of null check in sapmodule destructor in Snapdragon Auto, Snapdragon Consumer IOT, Snapdrag… qualcomm · mdm9607_firmware, qualcomm · msm8917_firmware, qualcomm · msm8920_firmware +9 2020-04-16 medium5.5 CVE-2019-14007 Due to the use of non-time-constant comparison functions there is issue in timing side channels which can be used as a potential side channel for SUI corruptio… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-04-16 medium5.5 CVE-2019-10608 Information disclosure issue occurs as there is no binding between the secure keypad session and the secure display session that allows user to take control of… qualcomm · apq8009_firmware, qualcomm · msm8905_firmware, qualcomm · msm8909_firmware 2020-04-16 medium5.5 CVE-2019-10523 Target specific data is being sent to remote server and leads to information exposure in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdrag… qualcomm · apq8009_firmware, qualcomm · apq8053_firmware, qualcomm · apq8096au_firmware +9 2020-04-16 medium5.5 CVE-2019-10483 Side channel issue in QTEE due to usage of non-time-constant comparison function such as memcmp or strcmp in Snapdragon Auto, Snapdragon Compute, Snapdragon Co… qualcomm · apq8009_firmware, qualcomm · apq8016_firmware, qualcomm · apq8017_firmware +9 2020-04-16 medium5.5 CVE-2019-10616 Possibility of null pointer access if the SPDM commands are executed in the non-standard way in TZ. qualcomm · apq8009_firmware, qualcomm · apq8016_firmware, qualcomm · mdm9150_firmware +9 2020-03-05 medium5.5 CVE-2019-10561 Improper initialization of local variables which are parameters to sfs api may cause invalid pointer dereference and leads to denial of service in Snapdragon A… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-01-21 medium5.5 CVE-2016-5346 An Information Disclosure vulnerability exists in the Google Pixel/Pixel SL Qualcomm Avtimer Driver due to a NULL pointer dereference when processing an accept… google · android 2020-01-08 medium5.5 CVE-2019-10513 Possibility of Null pointer access if the SPDM commands are executed in the non-standard way in Trustzone in Snapdragon Auto, Snapdragon Compute, Snapdragon Co… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2019-12-18 medium5.9 CVE-2019-10482 Due to the use of non-time-constant comparison functions there is issue in timing side channels which can be used as a potential side channel for SUI corruptio… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2019-12-18 medium5.5 CVE-2019-10618 Driver may access an invalid address while processing IO control due to lack of check of address validation in Snapdragon Connectivity in QCA6390 qualcomm · qca6390_firmware 2019-12-12 medium5.5 CVE-2019-10545 Null pointer dereference issue in kernel due to missing check related to LLC support in GPU in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, S… qualcomm · qcs605_firmware, qualcomm · sdm670_firmware, qualcomm · sdm710_firmware +3 2019-12-12 medium5.5 CVE-2019-10520 An unprivileged application can allocate GPU memory by calling memory allocation ioctl function and can exhaust all the memory which results in out of memory i… qualcomm · qcs405_firmware, qualcomm · sd_210_firmware, qualcomm · sd_212_firmware +9 2019-12-12 medium5.5 CVE-2019-10484 Use after free issue occurs when command destructors access dynamically allocated response buffer which is already deallocated during previous command teardwon… qualcomm · apq8098_firmware, qualcomm · msm8909w_firmware, qualcomm · nicobar_firmware +9 2019-12-12 medium5.5 CVE-2019-2336 Subsequent use of the CBO listener may result in further memory corruption due to use after free issue. qualcomm · mdm9205_firmware, qualcomm · qcs404_firmware, qualcomm · sdx55_firmware +4 2019-11-21 medium5.5 CVE-2019-2318 Non Secure Kernel can cause Trustzone to do an arbitrary memory read which will result into DOS in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consume… qualcomm · apq8017_firmware, qualcomm · apq8053_firmware, qualcomm · apq8096_firmware +9 2019-11-21 medium5.5 CVE-2019-2295 Information disclosure due to lack of address range check done on the SysDBG buffers in SDI code. qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2019-11-21 medium5.5 CVE-2019-10535 Improper validation for loop variable received from firmware can lead to out of bound access in WLAN function while iterating through loop in Snapdragon Auto, … qualcomm · apq8053_firmware, qualcomm · apq8096au_firmware, qualcomm · apq8098_firmware +9 2019-11-21 medium5.5 CVE-2019-10490 Use after free issue in Xtra daemon shutdown due to static object instance getting freed from a multiple places in Snapdragon Auto, Snapdragon Compute, Snapdra… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2019-11-21 medium6.5 CVE-2019-16401 Samsung Galaxy S8 plus (Android version: 8.0.0, Build Number: R16NW.G955USQU5CRG3, Baseband Vendor: Qualcomm Snapdragon 835, Baseband: G955USQU5CRG3), Samsung … samsung · galaxy_s8_plus_firmware, samsung · galaxy_s3_firmware, samsung · galaxy_note_2_firmware 2019-11-06 medium6.5 CVE-2019-16400 Samsung Galaxy S8 plus (Android version: 8.0.0, Build Number: R16NW.G955USQU5CRG3, Baseband Vendor: Qualcomm Snapdragon 835, Baseband: G955USQU5CRG3), Samsung … samsung · galaxy_s8_plus_firmware, samsung · galaxy_s3_firmware, samsung · galaxy_note_2_firmware 2019-11-06 medium5.5 CVE-2019-2275 While deserializing any key blob during key operations, buffer overflow could occur exposing partial key information if any key operations are invoked(Depends … qualcomm · mdm9150_firmware, qualcomm · mdm9205_firmware, qualcomm · mdm9206_firmware +9 2019-11-06 medium5.5 CVE-2019-10515 DCI client which might be preemptively freed up might be accessed for transferring packets leading to kernel error in Snapdragon Auto, Snapdragon Consumer IOT,… qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware +9 2019-11-06 medium6.5 CVE-2019-10504 Firmware not able to send EXT scan response to host within 1 sec due to resource consumption issue in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Indu… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · msm8909w_firmware +9 2019-11-06 medium5.5 CVE-2019-2343 Out of bound read and information disclosure in firmware due to insufficient checking of an embedded structure that can be sent from a kernel driver in Snapdra… qualcomm · msm8909w_firmware, qualcomm · msm8996au_firmware, qualcomm · qcs605_firmware +9 2019-07-25 medium5.5 CVE-2019-2330 improper input validation in allocation request for secure allocations can lead to page fault. qualcomm · ipq4019_firmware, qualcomm · ipq8064_firmware, qualcomm · ipq8074_firmware +9 2019-07-25 medium5.5 CVE-2019-2241 While rendering the layout background, Error status check is not caught properly and also incorrect status handling is being done leading to unintended SUI beh… qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware +9 2019-07-25 medium5.5 CVE-2019-2240 While sending the rendered surface content to the screen, Error handling is not properly checked results in an unpredictable behaviour in Snapdragon Auto, Snap… qualcomm · ipq4019_firmware, qualcomm · ipq8064_firmware, qualcomm · ipq8074_firmware +9 2019-07-25 medium5.5 CVE-2019-2239 Sanity checks are missing in layout which can lead to SUI Corruption or can lead to Denial of Service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connec… qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware +9 2019-07-25

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.