CVE-2013-5218

LOW2.9/ 10.0
Share:
Published: December 30, 2013 at 04:53 AM
Modified: April 11, 2025 at 12:51 AM
Source: cve@mitre.org

Vulnerability Description

Cross-site scripting (XSS) vulnerability on the HOT HOTBOX router with software 2.1.11 allows remote attackers to inject arbitrary web script or HTML via a crafted DHCP Host Name option, which is not properly handled during rendering of the DHCP table in wlanAccess.asp.

CVSS Metrics

Base Score
2.9
Severity
LOW
Vector String
AV:A/AC:M/Au:N/C:N/I:P/A:N

Weaknesses (CWE)

Source: nvd@nist.gov

AI Security Analysis

01 // Technical Summary

HOT HOTBOX routers running software version 2.1.11 are vulnerable to a cross-site scripting (XSS) attack. Attackers can inject malicious scripts into the router's web interface by crafting a malicious DHCP Host Name option, potentially leading to account compromise or device takeover.

02 // Vulnerability Mechanism

Step 1: Payload Preparation: The attacker crafts a malicious DHCP Host Name. This name includes HTML or JavaScript code designed to execute in the victim's browser. For example, <script>alert('XSS')</script>.

Step 2: DHCP Request: The attacker's device sends a DHCP request to the HOT HOTBOX router, including the crafted Host Name in the request.

Step 3: Router Configuration: The router receives the DHCP request and stores the malicious Host Name in its internal configuration.

Step 4: Webpage Access: A legitimate user accesses the wlanAccess.asp page on the router's web interface, typically to view the DHCP table.

Step 5: Vulnerable Rendering: The wlanAccess.asp page retrieves the DHCP Host Name from the router's configuration and renders it directly in the HTML output, without proper sanitization or encoding.

Step 6: Payload Execution: The user's browser interprets the injected HTML or JavaScript code, executing the attacker's payload. This could lead to various malicious actions, such as cookie theft, session hijacking, or redirection to a phishing site.

03 // Deep Technical Analysis

The vulnerability stems from a failure to properly sanitize user-supplied input from the DHCP Host Name option before rendering it within the wlanAccess.asp page. Specifically, the router's web application directly incorporates the DHCP Host Name into the HTML output without any form of input validation or output encoding. This allows an attacker to inject arbitrary HTML and JavaScript code. The root cause is a lack of contextual output encoding within the web application's code, leading to the execution of malicious scripts within the user's browser when they access the DHCP table.

CVE-2013-5218 - LOW Severity (2.9) | Free CVE Database | 4nuxd