NetSight

Security Dashboard

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

Reset
3,104 matching advisories · page 28 of 104Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.1 CVE-2022-33220 Information disclosure in Automotive multimedia due to buffer over-read. qualcomm · aqt1000_firmware, qualcomm · qam8295p_firmware, qualcomm · qca6390_firmware +9 2023-09-05 medium6.7 CVE-2023-28577 In the function call related to CAM_REQ_MGR_RELEASE_BUF there is no check if the buffer is being used. qualcomm · fastconnect_6800_firmware, qualcomm · fastconnect_6900_firmware, qualcomm · fastconnect_7800_firmware +9 2023-08-08 medium6.4 CVE-2023-28576 The buffer obtained from kernel APIs such as cam_mem_get_cpu_buf() may be readable/writable in userspace after kernel accesses it. qualcomm · fastconnect_6800_firmware, qualcomm · fastconnect_6900_firmware, qualcomm · fastconnect_7800_firmware +9 2023-08-08 medium6.7 CVE-2023-28575 The cam_get_device_priv function does not check the type of handle being returned (device/session/link). qualcomm · aqt1000_firmware, qualcomm · c-v2x_9150_firmware, qualcomm · fastconnect_6200_firmware +9 2023-08-08 critical9.8 CVE-2023-28561 Memory corruption in QESL while processing payload from external ESL device to firmware. qualcomm · qcn7606_firmware 2023-08-08 high7.5 CVE-2023-28555 Transient DOS in Audio while remapping channel buffer in media codec decoding. qualcomm · ar8035_firmware, qualcomm · wcn3991_firmware, qualcomm · wcn3998_firmware +9 2023-08-08 high8.4 CVE-2023-28537 Memory corruption while allocating memory in COmxApeDec module in Audio. qualcomm · 315_5g_iot_modem_firmware, qualcomm · apq8017_firmware, qualcomm · aqt1000_firmware +9 2023-08-08 high8.4 CVE-2023-22666 Memory Corruption in Audio while playing amrwbplus clips with modified content. qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8096au_firmware +9 2023-08-08 high7.7 CVE-2023-21652 Cryptographic issue in HLOS as derived keys used to encrypt/decrypt information is present on stack after use. qualcomm · aqt1000_firmware, qualcomm · ar8035_firmware, qualcomm · csra6620_firmware +9 2023-08-08 critical9.3 CVE-2023-21651 Memory Corruption in Core due to incorrect type conversion or cast in secure_io_read/write function in TEE. qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware, qualcomm · ar8035_firmware +9 2023-08-08 medium6.7 CVE-2023-21650 Memory Corruption in GPS HLOS Driver when injectFdclData receives data with invalid data length. qualcomm · aqt1000_firmware, qualcomm · csrb31024_firmware, qualcomm · qam8295p_firmware +9 2023-08-08 medium6.7 CVE-2023-21649 Memory corruption in WLAN while running doDriverCmd for an unspecific command. qualcomm · apq8096au_firmware, qualcomm · aqt1000_firmware, qualcomm · mdm9628_firmware +9 2023-08-08 medium6.7 CVE-2023-21648 Memory corruption in RIL while trying to send apdu packet. qualcomm · aqt1000_firmware, qualcomm · qca6391_firmware, qualcomm · qca6420_firmware +9 2023-08-08 medium6.5 CVE-2023-21647 Information disclosure in Bluetooth when an GATT packet is received due to improper input validation. qualcomm · qca6390_firmware, qualcomm · qca6391_firmware, qualcomm · qca6426_firmware +9 2023-08-08 critical9.1 CVE-2023-21643 Memory corruption due to untrusted pointer dereference in automotive during system call. qualcomm · apq8064au_firmware, qualcomm · apq8096au_firmware, qualcomm · msm8996au_firmware +9 2023-08-08 medium6.7 CVE-2023-21627 Memory corruption in Trusted Execution Environment while calling service API with invalid address. qualcomm · aqt1000_firmware, qualcomm · qca6390_firmware, qualcomm · qca6391_firmware +9 2023-08-08 high7.1 CVE-2023-21626 Cryptographic issue in HLOS due to improper authentication while performing key velocity checks using more than one key. qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8037_firmware +9 2023-08-08 high8.2 CVE-2023-21625 Information disclosure in Network Services due to buffer over-read while the device receives DNS response. qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8037_firmware +9 2023-08-08 critical9.8 CVE-2022-40510 Memory corruption due to buffer copy without checking size of input in Audio while voice call with EVS vocoder. qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware +9 2023-08-08 high7.8 CVE-2023-28542 Memory Corruption in WLAN HOST while fetching TX status information. qualcomm · 315_5g_iot_firmware, qualcomm · apq8064au_firmware, qualcomm · aqt1000_firmware +9 2023-07-04 high7.8 CVE-2023-28541 Memory Corruption in Data Modem while processing DMA buffer release event about CFR data. qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware, qualcomm · ar9380_firmware +9 2023-07-04 high7.8 CVE-2023-24854 Memory Corruption in WLAN HOST while parsing QMI WLAN Firmware response message. qualcomm · ar8035_firmware, qualcomm · csra6620_firmware, qualcomm · csra6640_firmware +9 2023-07-04 high7.8 CVE-2023-24851 Memory Corruption in WLAN HOST while parsing QMI response message from firmware. qualcomm · ar8035_firmware, qualcomm · csr8811_firmware, qualcomm · csra6620_firmware +9 2023-07-04 high8.4 CVE-2023-22667 Memory Corruption in Audio while allocating the ion buffer during the music playback. qualcomm · 315_5g_iot_firmware, qualcomm · apq8017_firmware, qualcomm · aqt1000_firmware +9 2023-07-04 high7.8 CVE-2023-22387 Arbitrary memory overwrite when VM gets compromised in TX write leading to Memory Corruption. qualcomm · 315_5g_iot_firmware, qualcomm · apq8017_firmware, qualcomm · aqt1000_firmware +9 2023-07-04 high7.8 CVE-2023-22386 Memory Corruption in WLAN HOST while processing WLAN FW request to allocate memory. qualcomm · ar8035_firmware, qualcomm · csr8811_firmware, qualcomm · csra6620_firmware +9 2023-07-04 high8.4 CVE-2023-21672 Memory corruption in Audio while running concurrent tunnel playback or during concurrent audio tunnel recording sessions. qualcomm · fastconnect_6700_firmware, qualcomm · fastconnect_6900_firmware, qualcomm · fastconnect_7800_firmware +9 2023-07-04 medium6.6 CVE-2023-21641 An app with non-privileged access can change global system brightness and cause undesired system behavior. qualcomm · fastconnect_6900_firmware, qualcomm · fastconnect_7800_firmware, qualcomm · qca6574au_firmware +9 2023-07-04 medium6.7 CVE-2023-21640 Memory corruption in Linux when the file upload API is called with parameters having large buffer. qualcomm · fastconnect_6900_firmware, qualcomm · fastconnect_7800_firmware, qualcomm · snapdragon_8_gen_1_firmware +3 2023-07-04 medium6.7 CVE-2023-21639 Memory corruption in Audio while processing sva_model_serializer using memory size passed by HIDL client. qualcomm · aqt1000_firmware, qualcomm · fastconnect_6200_firmware, qualcomm · qca6420_firmware +9 2023-07-04

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.