Stephen Fewer

Researcher fromRapid7
#529of 55,135
348.7Total CVSS
Vulnerabilities · 39
Medium
5
High
28
Critical
6
PT-2026-40959
10
2026-05-14
Cisco · Catalyst Sd-Wan Manager · CVE-2026-20182
**Name of the Vulnerable Software and Affected Versions** Cisco Catalyst SD-WAN Controller (affected versions not specified) Cisco Catalyst SD-WAN Manager (affected versions not specified) Cisco Catalyst SD-WAN Validator (affected versions not specified) **Description** A flaw in the peering authentication mechanism of the control connection handshaking allows an unauthenticated remote attacker to bypass authentication and obtain administrative privileges. The issue exists because the system fails to properly validate incoming certificates and tokens during inter-controller session setups, specifically within the `vdaemon` service. By sending crafted requests—such as a DTLS connection with a self-signed certificate—an attacker can mimic a trusted peer and be granted a high-privileged internal user account. This access enables the use of NETCONF to manipulate global routing tables, inject malicious routing policies, and modify network configurations across the entire SD-WAN fabric. The issue has been actively exploited in the wild by sophisticated threat actors, including the group UAT-8616, to deploy SSH keys, install web shells, and run cryptocurrency miners. **Recommendations** Update Cisco Catalyst SD-WAN Controller, Manager, and Validator to version 20.12.6.2 or newer. Restrict management-plane access to known administrative IP ranges via Access Control Lists (ACLs) to ensure the peering authentication endpoint is not reachable from arbitrary network sources. Restrict all inbound external access to NETCONF endpoints. Audit peering logs for unauthorized attachment sequences and inspect user databases for unauthorized secondary administrative accounts. Perform a diff analysis of global routing and security policy tables against known-good backup baselines to detect malicious traffic-mirroring paths.
PT-2025-6477
10
2025-02-12
Postgresql · Postgresql · CVE-2025-1094
**Name of the Vulnerable Software and Affected Versions** PostgreSQL versions prior to 17.3 PostgreSQL versions prior to 16.7 PostgreSQL versions prior to 15.11 PostgreSQL versions prior to 14.16 PostgreSQL versions prior to 13.19 **Description** The issue is related to improper neutralization of quoting syntax in PostgreSQL libpq functions, specifically `PQescapeLiteral()`, `PQescapeIdentifier()`, `PQescapeString()`, and `PQescapeStringConn()`. This allows a database input provider to achieve SQL injection in certain usage patterns, particularly when the application uses the function result to construct input to `psql`, the PostgreSQL interactive terminal. Similarly, improper neutralization of quoting syntax in PostgreSQL command line utility programs allows a source of command line arguments to achieve SQL injection when `client encoding` is BIG5 and `server encoding` is one of EUC TW or MULE INTERNAL. The vulnerability has been exploited in real-world attacks, including the US Treasury hack, and is considered high-severity. **Recommendations** For versions prior to 17.3, update to version 17.3 or later. For versions prior to 16.7, update to version 16.7 or later. For versions prior to 15.11, update to version 15.11 or later. For versions prior to 14.16, update to version 14.16 or later. For versions prior to 13.19, update to version 13.19 or later. As a temporary workaround, consider restricting access to the `psql` tool and limiting the use of the vulnerable libpq functions until a patch is applied.
PT-2021-6474
8.8
2021-12-03
NetGear · Netgear Xr300 · CVE-2022-27643
**Name of the Vulnerable Software and Affected Versions** NETGEAR R6400 versions prior to the fixed version NETGEAR R6400v2 versions prior to the fixed version NETGEAR R6700v3 version 1.0.4.120 10.0.91 NETGEAR R6900P versions prior to the fixed version NETGEAR R7000 versions prior to the fixed version NETGEAR R7000P versions prior to the fixed version NETGEAR R8500 versions prior to the fixed version NETGEAR RS400 versions prior to the fixed version NETGEAR WNDR3400v3 versions prior to the fixed version NETGEAR WNR3500Lv2 versions prior to the fixed version NETGEAR XR300 versions prior to the fixed version NETGEAR D6220 versions prior to the fixed version NETGEAR D6400 versions prior to the fixed version NETGEAR D7000v2 versions prior to the fixed version NETGEAR R7100LG versions prior to the fixed version NETGEAR DC112A versions prior to the fixed version **Description** The issue is related to a buffer overflow due to the lack of validation of the length of user-supplied data when handling SOAP requests, specifically when parsing the `SOAPAction` header. This allows an attacker to execute arbitrary code in the context of root without requiring authentication. The vulnerability can be exploited by network-adjacent attackers. **Recommendations** For NETGEAR R6400, update to a version that fixes the vulnerability. For NETGEAR R6400v2, update to a version that fixes the vulnerability. For NETGEAR R6700v3 version 1.0.4.120 10.0.91, update to a version that fixes the vulnerability. For NETGEAR R6900P, update to a version that fixes the vulnerability. For NETGEAR R7000, update to a version that fixes the vulnerability. For NETGEAR R7000P, update to a version that fixes the vulnerability. For NETGEAR R8500, update to a version that fixes the vulnerability. For NETGEAR RS400, update to a version that fixes the vulnerability. For NETGEAR WNDR3400v3, update to a version that fixes the vulnerability. For NETGEAR WNR3500Lv2, update to a version that fixes the vulnerability. For NETGEAR XR300, update to a version that fixes the vulnerability. For NETGEAR D6220, update to a version that fixes the vulnerability. For NETGEAR D6400, update to a version that fixes the vulnerability. For NETGEAR D7000v2, update to a version that fixes the vulnerability. For NETGEAR R7100LG, update to a version that fixes the vulnerability. For NETGEAR DC112A, update to a version that fixes the vulnerability. As a temporary workaround, consider disabling the handling of SOAP requests until a patch is available. Restrict access to the vulnerable `upnpd` service to minimize the risk of exploitation. Avoid using the `SOAPAction` header in SOAP requests to the affected routers until the issue is resolved.