NetSight

Security Dashboard

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

Reset
611 matching advisories · page 8 of 21Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2024-48714 In TP-Link TL-WDR7660 v1.0, the guestRuleJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerabili… tp-link · tl-wdr7660_firmware 2024-10-15 medium6.5 CVE-2024-48713 In TP-Link TL-WDR7660 1.0, the wacWhitelistJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerabi… tp-link · tl-wdr7660_firmware 2024-10-15 medium6.5 CVE-2024-48712 In TP-Link TL-WDR7660 1.0, the rtRuleJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerabilities. tp-link · tl-wdr7660_firmware 2024-10-15 medium6.5 CVE-2024-48710 In TP-Link TL-WDR7660 1.0, the wlanTimerRuleJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerab… tp-link · tl-wdr7660_firmware 2024-10-15 medium5.5 CVE-2024-46325 TP-Link WR740N V6 has a stack overflow vulnerability via the ssid parameter in /userRpm/popupSiteSurveyRpm.htm url. tp-link · wr740n_firmware 2024-10-07 high8.0 CVE-2024-46486 TP-LINK TL-WDR5620 v2.3 was discovered to contain a remote code execution (RCE) vulnerability via the httpProcDataSrv function. tp-link · tl-wdr5620_firmware 2024-10-04 medium4.3 CVE-2024-35495 An Information Disclosure vulnerability in the Telemetry component in TP-Link Kasa KP125M V1.0.0 and Tapo P125M 1.0.0 Build 220930 Rel.143947 allows attackers … 2024-09-30 high7.6 CVE-2024-46549 An issue in the TP-Link MQTT Broker and API gateway of TP-Link Kasa KP125M v1.0.3 allows attackers to establish connections by impersonating devices owned by o… 2024-09-30 medium6.3 CVE-2024-46548 TP-Link Tapo P125M and Kasa KP125M v1.0.3 was discovered to improperly validate certificates, allowing attackers to eavesdrop on communications and access sens… 2024-09-30 high8.0 CVE-2024-46313 TP-Link WR941ND V6 has a stack overflow vulnerability in the ssid parameter in /userRpm/popupSiteSurveyRpm.htm. tp-link · wr941nd_firmware 2024-09-30 medium6.5 CVE-2024-9284 A vulnerability was found in TP-LINK TL-WR841ND up to 20240920. tp-link · tl-wr841nd_firmware 2024-09-27 critical9.8 CVE-2024-42815 In the TP-Link RE365 V1_180213, there is a buffer overflow vulnerability due to the lack of length verification for the USER_AGENT field in /usr/bin/httpd. tp-link · re365_firmware 2024-08-19 medium5.4 CVE-2024-4224 An authenticated stored cross-site scripting (XSS) exists in the TP-Link TL-SG1016DE affecting version TL-SG1016DE(UN) V7.6_1.0.0 Build 20230616, which could a… 2024-07-15 medium6.8 CVE-2024-38471 Multiple TP-LINK products allow a network-adjacent attacker with an administrative privilege to execute arbitrary OS commands by restoring a crafted backup fil… 2024-07-04 high7.2 CVE-2024-21827 A leftover debug code vulnerability exists in the cli_server debug functionality of Tp-Link ER7206 Omada Gigabit VPN Router 1.4.1 Build 20240117 Rel.57421. tp-link · er7206_firmware 2024-06-25 medium6.3 CVE-2024-37662 TP-LINK TL-7DR5130 v1.0.23 is vulnerable to TCP DoS or hijacking attacks. tp-link · tl-7dr5130_firmware 2024-06-17 medium6.3 CVE-2024-37661 TP-LINK TL-7DR5130 v1.0.23 is vulnerable to forged ICMP redirect message attacks. tp-link · tl-7dr5130_firmware 2024-06-17 medium5.3 CVE-2023-30307 An issue discovered in TP-LINK TL-R473GP-AC, TP-LINK XDR6020, TP-LINK TL-R479GP-AC, TP-LINK TL-R4239G, TP-LINK TL-WAR1200L, and TP-LINK TL-R476G routers allows… 2024-05-28 medium4.2 CVE-2024-5244 TP-Link Omada ER605 Reliance on Security Through Obscurity Vulnerability. tp-link · omada_er605_firmware 2024-05-23 high7.5 CVE-2024-5243 TP-Link Omada ER605 Buffer Overflow Remote Code Execution Vulnerability. tp-link · omada_er605_firmware 2024-05-23 high7.5 CVE-2024-5242 TP-Link Omada ER605 Stack-based Buffer Overflow Remote Code Execution Vulnerability. tp-link · omada_er605_firmware 2024-05-23 high7.5 CVE-2024-5228 TP-Link Omada ER605 Comexe DDNS Response Handling Heap-based Buffer Overflow Remote Code Execution Vulnerability. tp-link · omada_er605_firmware 2024-05-23 high7.5 CVE-2024-5227 TP-Link Omada ER605 PPTP VPN username Command Injection Remote Code Execution Vulnerability. tp-link · omada_er605_firmware 2024-05-23 medium4.8 CVE-2024-31340 TP-Link Tether versions prior to 4.5.13 and TP-Link Tapo versions prior to 3.3.6 do not properly validate certificates, which may allow a remote unauthenticate… TP-Link Tether, TP-Link Tapo 2024-05-22 medium6.8 CVE-2023-50225 TP-Link TL-WR902AC dm_fillObjByStr Stack-based Buffer Overflow Remote Code Execution Vulnerability. tp-link · tl-wr902ac_firmware 2024-05-03 medium6.5 CVE-2023-50224 TP-Link TL-WR841N Authentication Bypass by Spoofing VulnerabilityExploited tp-link · tl-wr841n_firmware, tp-link · mr6400_firmware, tp-link · tl-wdr3600_firmware +9 2024-05-03 medium6.8 CVE-2023-44448 TP-Link Archer A54 libcmm.so dm_fillObjByStr Stack-based Buffer Overflow Remote Code Execution Vulnerability. tp-link · archer_a54_firmware 2024-05-03 medium6.5 CVE-2023-44447 TP-Link TL-WR902AC loginFs Improper Authentication Information Disclosure Vulnerability. tp-link · tl-wr902ac_firmware 2024-05-03 high8.0 CVE-2023-41184 TP-Link Tapo C210 ActiveCells Stack-based Buffer Overflow Remote Code Execution Vulnerability. tp-link · tapo_c210_firmware 2024-05-03 high8.8 CVE-2023-39471 TP-Link TL-WR841N ated_tp Command Injection Remote Code Execution Vulnerability. tp-link · tl-wr841n_firmware, tp-link · tl-wr840n_firmware 2024-05-03

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.