NetSight

Security Dashboard

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

Reset
660 matching advisories · page 7 of 22Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2019-14113 Buffer overflow can occur in In WLAN firmware while unwraping data using CCMP cipher suite during parsing of EAPOL handshake frame in Snapdragon Auto, Snapdrag… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-04-16 critical9.8 CVE-2019-14112 Potential buffer overflow while processing CBF frames due to lack of check of buffer length before copy in Snapdragon Auto, Snapdragon Compute, Snapdragon Cons… qualcomm · apq8098_firmware, qualcomm · ipq6018_firmware, qualcomm · ipq8074_firmware +9 2020-04-16 critical9.8 CVE-2019-14111 Possible buffer overflow while handling NAN reception of NMF in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics C… qualcomm · ipq6018_firmware, qualcomm · ipq8074_firmware, qualcomm · nicobar_firmware +9 2020-04-16 critical9.8 CVE-2019-14110 Buffer overflow can occur in function wlan firmware while copying association frame content if frame length is more than the maximum buffer size in case of SAP… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-04-16 critical9.1 CVE-2019-14033 Multiple Read overflows issue due to improper length check while decoding tau reject/tau accept/detach request/attach reject/attach accept in Snapdragon Auto, … qualcomm · apq8053_firmware, qualcomm · apq8096_firmware, qualcomm · apq8096au_firmware +9 2020-04-16 critical9.1 CVE-2019-14020 Multiple Read overflows issue due to improper length check while decoding dedicated_eps_bearer_req/ act_def_context_req/ cs_serv_notification/ emm_info/ guti_r… qualcomm · apq8053_firmware, qualcomm · apq8076_firmware, qualcomm · apq8096_firmware +9 2020-04-16 critical9.1 CVE-2019-14019 Multiple Read overflows issue due to improper length check while decoding RAU accept/PDN disconnect Rej/Modify EPS ctxt req/bearer resource alloc Rej/Deact EPs… qualcomm · apq8009_firmware, qualcomm · apq8053_firmware, qualcomm · apq8076_firmware +9 2020-04-16 critical9.1 CVE-2019-14011 Multiple Read overflows issue due to improper length check while decoding 3G attach accept/ SMS/ pdn connection reject/ esm data transport/ bearer modify conte… qualcomm · apq8009_firmware, qualcomm · apq8053_firmware, qualcomm · apq8096_firmware +9 2020-04-16 critical9.1 CVE-2019-10622 Out of bound memory access can happen while parsing ADSP message due to lack of check of size of payload received from userspace in Snapdragon Auto, Snapdragon… qualcomm · apq8009_firmware, qualcomm · apq8096au_firmware, qualcomm · ipq4019_firmware +9 2020-04-16 critical9.1 CVE-2019-10610 Possible buffer over read when trying to process SDP message Video media line with frame-size attribute in video Media line in Snapdragon Auto, Snapdragon Comp… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-04-16 critical9.8 CVE-2019-10609 Out of bound write can happen due to lack of check of array index value while calculating it. qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-04-16 critical9.8 CVE-2019-10589 Lack of length check of response buffer can lead to buffer over-flow while GP command response buffer handling in Snapdragon Auto, Snapdragon Compute, Snapdrag… qualcomm · apq8017_firmware, qualcomm · apq8053_firmware, qualcomm · apq8098_firmware +9 2020-04-16 critical9.8 CVE-2019-10588 Copying RTCP messages into the output buffer without checking the destination buffer size which could lead to a remote stack overflow. qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-04-16 critical9.1 CVE-2019-10551 String error while processing non standard SIP messages received can lead to buffer overread and then denial of service in Snapdragon Auto, Snapdragon Compute,… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-04-16 critical9.8 CVE-2018-21055 An issue was discovered on Samsung mobile devices with N(7.0) (Qualcomm models using MSM8996 chipsets) software. google · android 2020-04-08 critical9.8 CVE-2017-18645 An issue was discovered on Samsung mobile devices with M(6.x) and N(7.x) (Qualcomm chipsets) software. google · android 2020-04-08 critical9.8 CVE-2017-18681 An issue was discovered on Samsung Galaxy S5 mobile devices with software through 2016-12-20 (Qualcomm AP chipsets). samsung · galaxy_s5_firmware 2020-04-07 critical9.8 CVE-2019-20590 An issue was discovered on Samsung mobile devices with O(8.x) (Qualcomm chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20548 An issue was discovered on Samsung mobile devices with P(9.0) devices (Qualcomm chipsets) software. google · android 2020-03-24 critical9.8 CVE-2019-20537 An issue was discovered on Samsung mobile devices with P(9.0) (TEEGRIS and Qualcomm chipsets). google · android 2020-03-24 critical9.8 CVE-2019-2317 The secret key used to make the Initial Sequence Number in the TCP SYN packet could be brute forced and therefore can be predicted in Snapdragon Auto, Snapdrag… qualcomm · msm8905_firmware, qualcomm · msm8909_firmware, qualcomm · msm8917_firmware +9 2020-03-05 critical9.8 CVE-2019-2311 Possible buffer overflow in WLAN handler due to lack of validation of destination buffer size before copying it in Snapdragon Auto, Snapdragon Compute, Snapdra… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8096_firmware +9 2020-03-05 critical9.8 CVE-2019-2300 Possible buffer overflow in WLAN handler due to lack of validation of destination buffer size before copying into it in Snapdragon Auto, Snapdragon Compute, Sn… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-03-05 critical9.8 CVE-2019-14098 Possible buffer overflow in data offload handler due to lack of check of keydata length when copying data in Snapdragon Auto, Snapdragon Compute, Snapdragon Co… qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2020-03-05 critical9.8 CVE-2019-14097 Possible buffer overflow in WLAN Parser due to lack of length check when copying data in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdrag… qualcomm · apq8096_firmware, qualcomm · apq8096au_firmware, qualcomm · apq8098_firmware +9 2020-03-05 critical9.8 CVE-2019-14095 Buffer overflow occurs while processing LMP packet in which name length parameter exceeds value specified in BT-specification in Snapdragon Auto, Snapdragon Co… qualcomm · apq8009_firmware, qualcomm · apq8016_firmware, qualcomm · apq8017_firmware +9 2020-03-05 critical9.8 CVE-2019-14086 Possible integer overflow while checking the length of frame which is a 32 bit integer and is added to another 32 bit integer which can lead to unexpected resu… qualcomm · apq8098_firmware, qualcomm · mdm9607_firmware, qualcomm · msm8998_firmware +9 2020-03-05 critical9.8 CVE-2019-14083 While parsing Service Descriptor Extended Attribute received as part of SDF frame, there is a possibility that incorrect length is specified in the attribute l… qualcomm · apq8009_firmware, qualcomm · apq8053_firmware, qualcomm · apq8096_firmware +9 2020-03-05 critical9.1 CVE-2019-14082 Potential buffer over-read due to lack of bound check of memory offset passed in WLAN firmware in Snapdragon Compute, Snapdragon Consumer Electronics Connectiv… qualcomm · ipq8074_firmware, qualcomm · mdm9206_firmware, qualcomm · mdm9207c_firmware +3 2020-03-05 critical9.8 CVE-2019-14045 Possible buffer overflow while processing clientlog and serverlog due to lack of validation of data received in logs in Snapdragon Auto, Snapdragon Consumer IO… qualcomm · apq8096au_firmware, qualcomm · qcs605_firmware, qualcomm · sdm439_firmware +2 2020-03-05

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.