NetSight

Security Dashboard

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

Reset
559 matching advisories · page 7 of 19Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2023-28554 Information Disclosure in Qualcomm IPC while reading values from shared memory in VM. qualcomm · aqt1000_firmware, qualcomm · ar9380_firmware, qualcomm · c-v2x_9150_firmware +9 2023-11-07 medium6.1 CVE-2023-28553 Information Disclosure in WLAN Host when processing WMI event command. qualcomm · ar8035_firmware, qualcomm · ar9380_firmware, qualcomm · csr8811_firmware +9 2023-11-07 medium6.1 CVE-2023-28571 Information disclosure in WLAN HOST while processing the WLAN scan descriptor list during roaming scan. qualcomm · apq8064au_firmware, qualcomm · csrb31024_firmware, qualcomm · qca6390_firmware +9 2023-10-03 medium6.6 CVE-2023-28539 Memory corruption in WLAN Host when the firmware invokes multiple WMI Service Available command. qualcomm · ar8035_firmware, qualcomm · ar9380_firmware, qualcomm · csr8811_firmware +9 2023-10-03 medium6.7 CVE-2023-22384 Memory Corruption in VR Service while sending data using Fast Message Queue (FMQ). qualcomm · qca6574au_firmware, qualcomm · qca6696_firmware, qualcomm · sa6145p_firmware +6 2023-10-03 medium6.5 CVE-2023-21667 Transient DOS in Bluetooth HOST while passing descriptor to validate the blacklisted BT keyboard. qualcomm · qca6390_firmware, qualcomm · qca6391_firmware, qualcomm · qca6426_firmware +9 2023-09-05 medium6.7 CVE-2023-21663 Memory Corruption while accessing metadata in Display. qualcomm · aqt1000_firmware, qualcomm · qca6420_firmware, qualcomm · qca6430_firmware +9 2023-09-05 medium6.7 CVE-2023-21655 Memory corruption in Audio while validating and mapping metadata. qualcomm · qca6391_firmware, qualcomm · qca6574au_firmware, qualcomm · qca6696_firmware +9 2023-09-05 medium6.7 CVE-2023-21654 Memory corruption in Audio during playback session with audio effects enabled. qualcomm · apq8096au_firmware, qualcomm · aqt1000_firmware, qualcomm · mdm9150_firmware +9 2023-09-05 medium6.7 CVE-2023-21644 Memory corruption in RIL due to Integer Overflow while triggering qcril_uim_request_apdu request. qualcomm · aqt1000_firmware, qualcomm · qca6390_firmware, qualcomm · qca6391_firmware +9 2023-09-05 medium6.7 CVE-2023-21636 Memory Corruption due to improper validation of array index in Linux while updating adn record. qualcomm · aqt1000_firmware, qualcomm · qca6390_firmware, qualcomm · qca6391_firmware +9 2023-09-05 medium6.7 CVE-2022-40524 Memory corruption due to buffer over-read in Modem while processing SetNativeHandle RTP service. qualcomm · aqt1000_firmware, qualcomm · qca6390_firmware, qualcomm · qca6391_firmware +9 2023-09-05 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 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 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 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 medium6.7 CVE-2023-21638 Memory corruption in Video while calling APIs with different instance ID than the one received in initialization. qualcomm · aqt1000_firmware, qualcomm · fastconnect_6200_firmware, qualcomm · fastconnect_6800_firmware +9 2023-07-04 medium6.7 CVE-2023-21637 Memory corruption in Linux while calling system configuration APIs. qualcomm · aqt1000_firmware, qualcomm · fastconnect_6200_firmware, qualcomm · fastconnect_6800_firmware +9 2023-07-04 medium6.7 CVE-2023-21635 Memory Corruption in Data Network Stack & Connectivity when sim gets detected on telephony. qualcomm · aqt1000_firmware, qualcomm · csrb31024_firmware, qualcomm · fastconnect_6200_firmware +9 2023-07-04 medium6.7 CVE-2023-21633 Memory Corruption in Linux while processing QcRilRequestImsRegisterMultiIdentityMessage request. qualcomm · apq8064au_firmware, qualcomm · aqt1000_firmware, qualcomm · fastconnect_6200_firmware +9 2023-07-04 medium6.8 CVE-2023-21629 Memory Corruption in Modem due to double free while parsing the PKCS15 sim files. qualcomm · 315_5g_firmware, qualcomm · apq8017_firmware, qualcomm · apq8037_firmware +9 2023-07-04 medium6.2 CVE-2023-21624 Information disclosure in DSP Services while loading dynamic module. qualcomm · fastconnect_6700_firmware, qualcomm · fastconnect_6800_firmware, qualcomm · fastconnect_6900_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.