NetSight

Security Dashboard

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

Reset
559 matching advisories · page 11 of 19Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2021-1960 Improper handling of ASB-C broadcast packets with crafted opcode in LMP can lead to uncontrolled resource consumption in Snapdragon Auto, Snapdragon Compute, S… qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware, qualcomm · ar8035_firmware +9 2021-09-09 medium6.7 CVE-2021-1958 A race condition in fastrpc kernel driver for dynamic process creation can lead to use after free scenario in Snapdragon Auto, Snapdragon Connectivity, Snapdra… qualcomm · qca6574a_firmware, qualcomm · qca6574au_firmware, qualcomm · qca6595_firmware +9 2021-09-09 medium6.5 CVE-2021-1957 Improper Access Control when ACL link encryption is failed and ACL link is not disconnected during reconnection with paired device in Snapdragon Auto, Snapdrag… qualcomm · apq8017_firmware, qualcomm · qca6174a_firmware, qualcomm · qca6390_firmware +9 2021-09-09 medium6.5 CVE-2021-1956 Improper handling of ASB-U packet with L2CAP channel ID by slave host can lead to interference with piconet in Snapdragon Auto, Snapdragon Compute, Snapdragon … qualcomm · aqt1000_firmware, qualcomm · ar8035_firmware, qualcomm · csrb31024_firmware +9 2021-09-09 medium5.5 CVE-2021-1930 Possible out of bounds read due to incorrect validation of incoming buffer length in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon C… qualcomm · aqt1000_firmware, qualcomm · csrb31024_firmware, qualcomm · qca6174a_firmware +9 2021-09-08 medium6.2 CVE-2021-1929 Lack of strict validation of bootmode can lead to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer I… qualcomm · apq8096au_firmware, qualcomm · aqt1000_firmware, qualcomm · msm8996au_firmware +9 2021-09-08 medium4.6 CVE-2021-1928 Buffer over read could occur due to incorrect check of buffer size while flashing emmc devices in Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon … qualcomm · apq8009_firmware, qualcomm · apq8053_firmware, qualcomm · ar9380_firmware +9 2021-09-08 medium6.2 CVE-2021-1904 Child process can leak information from parent process due to numeric pids are getting compared and these pid can be reused in Snapdragon Auto, Snapdragon Comp… qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware +9 2021-09-08 medium6.7 CVE-2021-1931 Possible buffer overflow due to improper validation of buffer length while processing fast boot commands in Snapdragon Auto, Snapdragon Compute, Snapdragon Con… qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware, qualcomm · ar8035_firmware +9 2021-07-13 medium4.6 CVE-2021-1901 Possible buffer over-read due to lack of length check while flashing meta images in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snap… qualcomm · apq8009_firmware, qualcomm · apq8053_firmware, qualcomm · aqt1000_firmware +9 2021-07-13 medium4.6 CVE-2021-1899 Possible buffer over read due to lack of length check while flashing meta images in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snap… qualcomm · apq8009w_firmware, qualcomm · aqt1000_firmware, qualcomm · msm8909w_firmware +9 2021-07-13 medium4.6 CVE-2021-1898 Possible buffer over-read due to incorrect overflow check when loading splash image in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, S… qualcomm · apq8009_firmware, qualcomm · apq8053_firmware, qualcomm · aqt1000_firmware +9 2021-07-13 medium4.6 CVE-2021-1897 Possible Buffer Over-read due to lack of validation of boundary checks when loading splash image in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdra… qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8053_firmware +9 2021-07-13 medium4.3 CVE-2021-1896 Weak configuration in WLAN could cause forwarding of unencrypted packets from one client to another in Snapdragon Compute, Snapdragon Connectivity qualcomm · aqt1000_firmware, qualcomm · qca6164_firmware, qualcomm · qca6174_firmware +9 2021-07-13 medium6.5 CVE-2020-11266 Image address is dereferenced before validating its range which can cause potential QSEE information leakage in Snapdragon Wired Infrastructure and Networking qualcomm · ar7420_firmware, qualcomm · ar9580_firmware, qualcomm · csr8811_firmware +9 2021-06-09 medium5.5 CVE-2020-11265 Information disclosure issue due to lack of validation of pointer arguments passed to TZ BSP in Snapdragon Wired Infrastructure and Networking qualcomm · ar7420_firmware, qualcomm · ar9580_firmware, qualcomm · csr8811_firmware +9 2021-06-09 medium6.7 CVE-2020-11160 Resource leakage issue during dci client registration due to reference count is not decremented if dci client registration fails in Snapdragon Auto, Snapdragon… qualcomm · apq8096au_firmware, qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware +9 2021-06-09 medium6.2 CVE-2021-1906 Qualcomm Multiple Chipsets Detection of Error Condition Without Action VulnerabilityExploited qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware +9 2021-05-07 medium6.8 CVE-2021-1895 Possible integer overflow due to improper length check while flashing an image in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware, qualcomm · apq8053_firmware +9 2021-05-07 medium6.8 CVE-2020-11295 Use after free in camera If the threadmanager is being cleaned up while the worker thread is processing objects in Snapdragon Auto, Snapdragon Compute, Snapdra… qualcomm · fsm10055_firmware, qualcomm · fsm10056_firmware, qualcomm · pm3003a_firmware +9 2021-05-07 medium5.9 CVE-2020-11294 Out of bound write in logger due to prefix size is not validated while prepended to logging string in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectiv… qualcomm · ar8035_firmware, qualcomm · pm215_firmware, qualcomm · pm3003a_firmware +9 2021-05-07 medium5.1 CVE-2020-11293 Out of bound read can happen in Widevine TA while copying data to buffer from user data due to lack of check of buffer length received in Snapdragon Auto, Snap… qualcomm · apq8017_firmware, qualcomm · apq8037_firmware, qualcomm · apq8053_firmware +9 2021-05-07 medium6.2 CVE-2020-11254 Memory corruption during buffer allocation due to dereferencing session ctx pointer without checking if pointer is valid in Snapdragon Auto, Snapdragon Compute… qualcomm · pm6150a, qualcomm · pm6150l, qualcomm · pm6350 +9 2021-05-07 medium6.7 CVE-2020-11231 Two threads call one or both functions concurrently leading to corruption of pointers and reference counters which in turn can lead to heap corruption in Snapd… qualcomm · apq8017_firmware, qualcomm · apq8053_firmware, qualcomm · aqt1000_firmware +9 2021-04-07 medium6.8 CVE-2020-11308 Buffer overflow occurs when trying to convert ASCII string to Unicode string if the actual size is more than required in Snapdragon Auto, Snapdragon Compute, S… qualcomm · apq8009_firmware, qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware +9 2021-03-17 medium6.8 CVE-2020-11305 Integer overflow in boot due to improper length check on arguments received in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music qualcomm · apq8009_firmware, qualcomm · apq8053_firmware, qualcomm · mdm9206_firmware +9 2021-03-17 medium6.4 CVE-2020-11230 Potential arbitrary memory corruption when the qseecom driver updates ion physical addresses in the buffer as it exposes a physical address to user land in Sna… qualcomm · aqt1000_firmware, qualcomm · fsm10055_firmware, qualcomm · pm3003a_firmware +9 2021-03-17 medium5.5 CVE-2020-11221 Usage of syscall by non-secure entity can allow extraction of secure QTEE diagnostic information in clear text form due to insufficient checks in the syscall h… qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware +9 2021-03-17 medium6.4 CVE-2020-11220 While processing storage SCM commands there is a time of check or time of use window where a pointer used could be invalid at a specific time while executing t… qualcomm · aqt1000_firmware, qualcomm · ar8035_firmware, qualcomm · pm4125_firmware +9 2021-03-17 medium5.5 CVE-2020-11199 HLOS to access EL3 stack canary by just mapping imem region due to Improper access control and can lead to information exposure in Snapdragon Auto, Snapdragon … qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware +9 2021-03-17

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.