NetSight

Security Dashboard

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

Reset
3,104 matching advisories · page 32 of 104Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.4 CVE-2022-40531 Memory corruption in WLAN due to incorrect type cast while sending WMI_SCAN_SCH_PRIO_TBL_CMDID message. qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8076_firmware +9 2023-03-10 high8.4 CVE-2022-40530 Memory corruption in WLAN due to integer overflow to buffer overflow in WLAN during initialization phase. qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware, qualcomm · ar8035_firmware +9 2023-03-10 high7.5 CVE-2022-40527 Transient DOS due to reachable assertion in WLAN while processing PEER ID populated by TQM. qualcomm · ar8035_firmware, qualcomm · csr8811_firmware, qualcomm · ipq5010_firmware +9 2023-03-10 high7.3 CVE-2022-40515 Memory corruption in Video due to double free while playing 3gp clip with invalid metadata atoms. qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8052_firmware +9 2023-03-10 high7.5 CVE-2022-33309 Transient DOS due to buffer over-read in WLAN Firmware while parsing secure FTMR frame with size lesser than 39 Bytes. qualcomm · csr8811_firmware, qualcomm · ipq5010_firmware, qualcomm · ipq5018_firmware +9 2023-03-10 high7.8 CVE-2022-33278 Memory corruption due to buffer copy without checking the size of input in HLOS when input message size is larger than the buffer capacity. qualcomm · aqt1000_firmware, qualcomm · ar8035_firmware, qualcomm · csra6620_firmware +9 2023-03-10 high7.5 CVE-2022-33272 Transient DOS in modem due to reachable assertion. qualcomm · ar8035_firmware, qualcomm · qca6390_firmware, qualcomm · qca6391_firmware +9 2023-03-10 medium5.9 CVE-2022-33260 Memory corruption due to stack based buffer overflow in core while sending command from USB of large size. qualcomm · aqt1000_firmware, qualcomm · qam8295p_firmware, qualcomm · qca6420_firmware +9 2023-03-10 critical9.3 CVE-2022-33257 Memory corruption in Core due to time-of-check time-of-use race condition during dump collection in trust zone. qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware, qualcomm · ar8035_firmware +9 2023-03-10 critical9.8 CVE-2022-33256 Memory corruption due to improper validation of array index in Multi-mode call processor. qualcomm · ar8035_firmware, qualcomm · qca6390_firmware, qualcomm · qca6391_firmware +9 2023-03-10 high7.5 CVE-2022-33254 Transient DOS due to reachable assertion in Modem while processing SIB1 Message. qualcomm · aqt1000_firmware, qualcomm · ar8035_firmware, qualcomm · qca6390_firmware +9 2023-03-10 high7.5 CVE-2022-33250 Transient DOS due to reachable assertion in modem when network repeatedly sent invalid message container for NR to LTE handover. qualcomm · ar8035_firmware, qualcomm · qca6390_firmware, qualcomm · qca6391_firmware +9 2023-03-10 medium6.7 CVE-2022-33245 Memory corruption in WLAN due to use after free qualcomm · apq8064au_firmware, qualcomm · apq8096au_firmware, qualcomm · aqt1000_firmware +9 2023-03-10 high7.5 CVE-2022-33244 Transient DOS due to reachable assertion in modem during MIB reception and SIB timeout qualcomm · ar8035_firmware, qualcomm · qca6391_firmware, qualcomm · qca8081_firmware +9 2023-03-10 high7.8 CVE-2022-33242 Memory corruption due to improper authentication in Qualcomm IPC while loading unsigned lib in audio PD. qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware, qualcomm · ar8035_firmware +9 2023-03-10 high7.5 CVE-2022-33213 Memory corruption in modem due to buffer overflow while processing a PPP packet qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware +9 2023-03-10 high8.4 CVE-2022-25709 Memory corruption in modem due to use of out of range pointer offset while processing qmi msg qualcomm · ar8035_firmware, qualcomm · qca6174a_firmware, qualcomm · qca6310_firmware +9 2023-03-10 high7.8 CVE-2022-25705 Memory corruption in modem due to integer overflow to buffer overflow while handling APDU response qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware +9 2023-03-10 high8.4 CVE-2022-25694 Memory corruption in Modem due to usage of Out-of-range pointer offset in UIM qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware, qualcomm · apq8037_firmware +9 2023-03-10 high8.4 CVE-2022-25655 Memory corruption in WLAN HAL while arbitrary value is passed in WMI UTF command payload. qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8076_firmware +9 2023-03-10 medium6.2 CVE-2022-22075 Information Disclosure in Graphics during GPU context switch. qualcomm · apq8009_firmware, qualcomm · apq8009w_firmware, qualcomm · apq8017_firmware +9 2023-03-10 critical9.8 CVE-2022-40514 Memory corruption due to buffer copy without checking the size of input in WLAN Firmware while processing CCKM IE in reassoc response frame. qualcomm · aqt1000_firmware, qualcomm · ar8031_firmware, qualcomm · ar8035_firmware +9 2023-02-12 high7.5 CVE-2022-40513 Transient DOS due to uncontrolled resource consumption in WLAN firmware when peer is freed in non qos state. qualcomm · csr8811_firmware, qualcomm · ipq5010_firmware, qualcomm · ipq5018_firmware +9 2023-02-12 high7.5 CVE-2022-40512 Transient DOS in WLAN Firmware due to buffer over-read while processing probe response or beacon. qualcomm · apq8009_firmware, qualcomm · apq8017_firmware, qualcomm · apq8064au_firmware +9 2023-02-12 high7.5 CVE-2022-40502 Transient DOS due to improper input validation in WLAN Host. qualcomm · csr8811_firmware, qualcomm · ipq5010_firmware, qualcomm · ipq5018_firmware +9 2023-02-12 high7.5 CVE-2022-34146 Transient DOS due to improper input validation in WLAN Host while parsing frame during defragmentation. qualcomm · csr8811_firmware, qualcomm · ipq5010_firmware, qualcomm · ipq5018_firmware +9 2023-02-12 high7.5 CVE-2022-34145 Transient DOS due to buffer over-read in WLAN Host while parsing frame information. qualcomm · csr8811_firmware, qualcomm · ipq5010_firmware, qualcomm · ipq5018_firmware +9 2023-02-12 high7.5 CVE-2022-33306 Transient DOS due to buffer over-read in WLAN while processing an incoming management frame with incorrectly filled IEs. qualcomm · ar8035_firmware, qualcomm · ar9380_firmware, qualcomm · csr8811_firmware +9 2023-02-12 high7.3 CVE-2022-33280 Memory corruption due to access of uninitialized pointer in Bluetooth HOST while processing the AVRCP packet. qualcomm · apq8096au_firmware, qualcomm · ar8031_firmware, qualcomm · ar8035_firmware +9 2023-02-12 critical9.8 CVE-2022-33279 Memory corruption due to stack based buffer overflow in WLAN having invalid WNM frame length. qualcomm · ar9380_firmware, qualcomm · csr8811_firmware, qualcomm · ipq4019_firmware +9 2023-02-12

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.