Session Smart Router: Vulnérabilité de contournement d'authentification

The authentication bypass vulnerability allows an attacker to exploit a flaw in the router's internal HTTP header handling. Successful exploitation grants the attacker a wide range of capabilities, including the ability to view internal files, modify router settings, manipulate services, and ultimately, execute arbitrary code. This represents a significant security risk, potentially leading to complete compromise of the router and any systems connected to it. The ability to execute arbitrary code means an attacker could install malware, redirect network traffic, or launch further attacks against internal resources. The impact is particularly severe given the router's role as a network gateway.

Organizations relying on 128 Technology Session Smart Routers as their primary network gateway are at significant risk. This includes small to medium-sized businesses, remote offices, and any environment where the router is exposed to the internet without adequate security controls. Shared hosting environments utilizing these routers are particularly vulnerable due to the potential for cross-tenant exploitation.

• linux / server: Monitor router logs (e.g., /var/log/router.log) for unusual HTTP requests or authentication attempts from unauthorized IP addresses. Use journalctl -u router to filter for authentication-related events. • generic web: Use curl -I <router_ip> to check for unexpected HTTP headers or responses indicating unauthorized access. • windows / supply-chain: (Less applicable, but if router management is accessed via Windows) Monitor PowerShell execution logs for suspicious commands related to router configuration or file access.

1. 2021-10-19Disclosure

   disclosure

1. Réservé2021-04-15
2. Publiée2021-10-19
3. Modifiée2024-09-16
4. EPSS mis à jour2026-04-02

The primary mitigation for CVE-2021-31349 is to upgrade the 128 Technology Session Smart Router to version 4.5.11 or later. If an immediate upgrade is not feasible due to compatibility concerns or system downtime requirements, consider implementing temporary workarounds. While no direct WAF rules can prevent this, strict access control lists (ACLs) limiting access to the router's management interface from untrusted networks can reduce the attack surface. Regularly review router configurations and disable any unnecessary services to minimize potential impact. After upgrading, verify the fix by attempting to access internal files or router settings without proper authentication.