NetSight

Security Dashboard

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

Reset
428 matching advisories · page 7 of 15Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2024-37607 A Buffer overflow vulnerability in D-Link DAP-2555 REVA_FIRMWARE_1.20 allows remote attackers to cause a Denial of Service (DoS) via a crafted HTTP request. dlink · dap-2555_firmware 2024-12-17 medium6.5 CVE-2024-37606 A Stack overflow vulnerability in D-Link DCS-932L REVB_FIRMWARE_2.18.01 allows attackers to cause a Denial of Service (DoS) via a crafted HTTP request. dlink · dcs-932l_firmware 2024-12-17 medium6.5 CVE-2024-37605 A NULL pointer dereference in D-Link DIR-860L REVB_FIRMWARE_2.04.B04_ic5b allows attackers to cause a Denial of Service (DoS) via a crafted HTTP request. dlink · dir-860l_firmware 2024-12-17 medium5.3 CVE-2024-36831 A NULL pointer dereference in the plugins_call_handle_uri_clean function of D-Link DAP-1520 REVA_FIRMWARE_1.10B04_BETA02_HOTFIX allows attackers to cause a Den… dlink · dap-1520_firmware 2024-12-17 medium4.9 CVE-2024-52755 D-LINK DI-8003 v16.07.26A1 was discovered to contain a buffer overflow via the host_ip parameter in the ipsec_road_asp function. dlink · di-8003_firmware 2024-11-21 medium4.9 CVE-2024-52757 D-LINK DI-8003 v16.07.16A1 was discovered to contain a buffer overflow via the notify parameter in the arp_sys_asp function. dlink · di-8003_firmware 2024-11-20 medium4.9 CVE-2024-52754 D-LINK DI-8003 v16.07.16A1 was discovered to contain a buffer overflow via the fn parameter in the tgfile_htm function. dlink · di-8003_firmware 2024-11-20 medium5.7 CVE-2024-52711 DI-8100 v16.07.26A1 is vulnerable to Buffer Overflow In the ip_position_asp function via the ip parameter. dlink · di-8100_firmware 2024-11-19 medium4.3 CVE-2024-28731 Cross Site Request Forgery vulnerability in DLink DWR 2000M 5G CPE With Wifi 6 Ax1800 and Dlink DWR 5G CPE DWR-2000M_1.34ME allows a local attacker to obtain s… dlink · dwr-2000m_firmware 2024-11-12 medium5.4 CVE-2024-28730 Cross Site Scripting vulnerability in DLink DWR 2000M 5G CPE With Wifi 6 Ax1800 and Dlink DWR 5G CPE DWR-2000M_1.34ME allows a local attacker to obtain sensiti… dlink · dwr-2000m_firmware 2024-11-12 medium6.6 CVE-2024-28728 Cross Site Scripting vulnerability in DLink DWR 2000M 5G CPE With Wifi 6 Ax1800 and Dlink DWR 5G CPE DWR-2000M_1.34ME allows a local attacker to obtain sensiti… 2024-11-12 medium6.3 CVE-2024-11046 A vulnerability was found in D-Link DI-8003 16.07.16A1. dlink · di-8003_firmware 2024-11-10 medium5.3 CVE-2024-10916 A vulnerability classified as problematic has been found in D-Link DNS-320, DNS-320LW, DNS-325 and DNS-340L up to 20241028. dlink · dns-320_firmware, dlink · dns-320lw_firmware, dlink · dns-325_firmware +1 2024-11-06 medium6.5 CVE-2024-48272 D-Link DSL6740C v6.TR069.20211230 was discovered to use an insecure default Wifi password, possibly allowing attackers to connect to the device via a bruteforc… dlink · dsl-6740c_firmware 2024-10-30 medium5.5 CVE-2024-9908 A vulnerability, which was classified as critical, was found in D-Link DIR-619L B1 2.06. dlink · dir-619l_firmware 2024-10-13 medium5.7 CVE-2024-44674 D-Link COVR-2600R FW101b05 is vulnerable to Buffer Overflow. dlink · covr-2600r_firmware 2024-10-07 medium4.3 CVE-2024-6051 Cross Application Scripting vulnerability in Vercom S.A. Redlink SDK 2024-09-30 medium6.3 CVE-2024-9004 A vulnerability classified as critical has been found in D-Link DAR-7000 up to 20240912. dlink · dar-7000_firmware 2024-09-19 medium5.3 CVE-2024-8461 A vulnerability, which was classified as problematic, was found in D-Link DNS-320 2.02b01. dlink · dns-320_firmware 2024-09-05 medium6.3 CVE-2024-8214 A vulnerability classified as critical was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-… dlink · dns-315l_firmware, dlink · dns-320lw_firmware, dlink · dns-1550-04_firmware +9 2024-08-27 medium6.3 CVE-2024-8213 A vulnerability classified as critical has been found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325,… dlink · dns-315l_firmware, dlink · dns-320lw_firmware, dlink · dns-1550-04_firmware +9 2024-08-27 medium6.3 CVE-2024-8212 A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326,… dlink · dns-315l_firmware, dlink · dns-320lw_firmware, dlink · dns-1550-04_firmware +9 2024-08-27 medium6.3 CVE-2024-8211 A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326,… dlink · dns-315l_firmware, dlink · dns-320lw_firmware, dlink · dns-1550-04_firmware +9 2024-08-27 medium6.3 CVE-2024-8210 A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326,… dlink · dns-315l_firmware, dlink · dns-320lw_firmware, dlink · dns-1550-04_firmware +9 2024-08-27 medium6.3 CVE-2024-8134 A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326,… dlink · dns-1550-04_firmware, dlink · dns-1200-05_firmware, dlink · dns-1100-4_firmware +9 2024-08-24 medium6.3 CVE-2024-8133 A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326,… dlink · dns-1550-04_firmware, dlink · dns-1200-05_firmware, dlink · dns-1100-4_firmware +9 2024-08-24 medium6.3 CVE-2024-8132 A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326,… dlink · dns-1550-04_firmware, dlink · dns-1200-05_firmware, dlink · dns-1100-4_firmware +9 2024-08-24 medium6.3 CVE-2024-8131 A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326,… dlink · dns-1550-04_firmware, dlink · dns-1200-05_firmware, dlink · dns-1100-4_firmware +9 2024-08-24 medium6.3 CVE-2024-8130 A vulnerability has been found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR… dlink · dns-1550-04_firmware, dlink · dns-1200-05_firmware, dlink · dns-1100-4_firmware +9 2024-08-24 medium6.3 CVE-2024-8129 A vulnerability, which was classified as critical, was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, D… dlink · dns-1550-04_firmware, dlink · dns-1200-05_firmware, dlink · dns-1100-4_firmware +9 2024-08-24

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.