NetSight

Security Dashboard

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

Reset
559 matching advisories · page 14 of 19Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2019-2237 Failure in taking appropriate action to handle the error case If keypad gpio deactivation fails leads to silent failure scenario and subsequent logic gets exec… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2019-07-25 medium5.5 CVE-2019-2236 Null pointer dereference during secure application termination using specific application ids. qualcomm · ipq8074_firmware, qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware +9 2019-07-25 medium5.5 CVE-2019-2261 Unauthorized access from GPU subsystem to HLOS or other non secure subsystem memory can lead to information disclosure in Snapdragon Auto, Snapdragon Compute, … qualcomm · ipq8074_firmware, qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware +9 2019-07-22 medium5.5 CVE-2019-2243 Possible buffer overflow at the end of iterating loop while getting the version info and lead to information disclosure. qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2019-07-22 medium5.3 CVE-2018-13907 While deserializing any key blob during key operations, buffer overflow could occur, exposing partial key information if any key operations are invoked in Snap… qualcomm · pq4019_firmware, qualcomm · ipq8074_firmware, qualcomm · mdm9150_firmware +9 2019-06-14 medium5.5 CVE-2018-13901 Due to missing permissions in Android Manifest file, Sensitive information disclosure issue can happen in PCI RCS app in Snapdragon Auto, Snapdragon Connectivi… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2019-06-14 medium5.5 CVE-2018-11947 The txrx stats req might be double freed in the pdev detach when the host driver is unloading in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity,… qualcomm · ipq8064_firmware, qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware +9 2019-06-14 medium5.5 CVE-2018-11942 Failure to initialize the reserved memory which is sent to the firmware might lead to exposure of 1 byte of uninitialized kernel SKB memory to FW in Snapdragon… qualcomm · ipq4019_firmware, qualcomm · ipq8064_firmware, qualcomm · ipq8074_firmware +9 2019-06-14 medium5.5 CVE-2017-8252 Kernel can inject faults in computations during the execution of TrustZone leading to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon… qualcomm · ipq4019_firmware, qualcomm · ipq8074_firmware, qualcomm · mdm9150_firmware +9 2019-06-14 medium5.5 CVE-2018-13885 Possible memory overread may be lead to access of sensitive data in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Sn… qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware +9 2019-05-24 medium5.5 CVE-2018-12005 An unprivileged user can issue a binder call and cause a system halt in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT… qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware +9 2019-05-24 medium5.5 CVE-2018-12004 Secure keypad is unlocked with secure display still intact in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Con… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2019-05-24 medium5.5 CVE-2018-11976 ECDSA signature code leaks private keys from secure world to non-secure world in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consu… qualcomm · ipq8074_firmware, qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware +9 2019-05-24 medium5.5 CVE-2017-18275 A new account can be inserted into simContacts service using Android command line tool in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in MDM9206,… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2019-05-06 medium5.5 CVE-2017-15841 When HOST sends a Special command ID packet, Controller triggers a RAM Dump and FW reset in Snapdragon Mobile in version SD 410/12, SD 425, SD 427, SD 430, SD … qualcomm · sd_410_firmware, qualcomm · sd_412_firmware, qualcomm · sd_425_firmware +9 2019-05-06 medium5.5 CVE-2018-11971 Interrupt exit code flow may undermine access control policy set forth by secure world can lead to potential secure asset leakage in Snapdragon Auto, Snapdrago… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2019-04-04 medium5.5 CVE-2018-11958 Insufficient protection of keys in keypad can lead HLOS to gain access to confidential keypad input data in Snapdragon Auto, Snapdragon Consumer Electronics Co… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2019-04-04 medium5.5 CVE-2018-13912 Arbitrary write issue can occur when user provides kernel address in compat mode in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdrag… qualcomm · snapdragon_auto_firmware, qualcomm · snapdragon_connectivity_firmware, qualcomm · snapdragon_consumer_internet_of_things_firmware +9 2019-02-25 medium5.5 CVE-2018-11948 Exceeding the limit of usage entries are not tracked and the information will be lost causing the content to lose continuity in Snapdragon Auto, Snapdragon Com… qualcomm · msm8996au_firmware, qualcomm · qcs605_firmware, qualcomm · sd_410_firmware +9 2019-02-25 medium5.3 CVE-2018-11935 Improper input validation might result in incorrect app id returned to the caller Instead of returning failure in Snapdragon Auto, Snapdragon Compute, Snapdrag… qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware, qualcomm · mdm9655_firmware +9 2019-02-25 medium5.5 CVE-2018-11864 Bytes can be written to fuses from Secure region which can be read later by HLOS in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Co… qualcomm · ipq8074_firmware, qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware +9 2019-02-25 medium5.5 CVE-2018-11845 Usage of non-time-constant comparison functions can lead to information leakage through side channel analysis in Snapdragon Auto, Snapdragon Compute, Snapdrago… qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware +9 2019-02-25 medium5.5 CVE-2018-11820 Use of non-time constant memcmp function creates side channel that leaks information and leads to cryptographic issues in Snapdragon Auto, Snapdragon Compute, … qualcomm · ipq8074_firmware, qualcomm · mdm9150_firmware, qualcomm · mdm9206_firmware +9 2019-02-25 medium5.5 CVE-2018-3595 Anti-rollback can be bypassed in replay scenario during app loading due to improper error handling of RPMB writes in snapdragon automobile, snapdragon mobile a… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9650_firmware +9 2019-01-18 medium5.5 CVE-2018-11999 Improper input validation in trustzone can lead to denial of service in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9206, MDM96… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9635m_firmware +9 2019-01-18 medium5.5 CVE-2017-18332 Security keys are logged when any WCDMA call is configured or reconfigured in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9607,… qualcomm · mdm9607_firmware, qualcomm · mdm9635m_firmware, qualcomm · mdm9640_firmware +9 2019-01-18 medium5.5 CVE-2017-18327 Security keys are logged when any WCDMA call is configured or reconfigured in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9607,… qualcomm · mdm9607_firmware, qualcomm · mdm9635m_firmware, qualcomm · mdm9640_firmware +9 2019-01-03 medium5.5 CVE-2017-18326 Cryptographic keys are printed in modem debug messages in snapdragon mobile and snapdragon wear in versions MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM96… qualcomm · mdm9607_firmware, qualcomm · mdm9615_firmware, qualcomm · mdm9625_firmware +9 2019-01-03 medium5.5 CVE-2017-18324 Cryptographic key material leaked in debug messages - GERAN in snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, … qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9615_firmware +9 2019-01-03 medium5.5 CVE-2017-18323 Cryptographic key material leaked in TDSCDMA RRC debug messages in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, M… qualcomm · mdm9206_firmware, qualcomm · mdm9607_firmware, qualcomm · mdm9615_firmware +9 2019-01-03

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.