CVE-2018-7633

9.8 CRITICAL

📋 TL;DR

This vulnerability allows attackers to inject and execute arbitrary JavaScript code through the Language parameter in the /ui/login form of Epicentro E firmware. Attackers can exploit this by tricking users into making manipulated POST requests, potentially leading to session hijacking, credential theft, or further system compromise. Affected systems are ADB firmware Epicentro E version 7.3.2 and potentially later versions.

💻 Affected Systems

Products:
  • ADB firmware Epicentro E
Versions: 7.3.2+
Operating Systems: Embedded firmware
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the web interface login form specifically. Requires user interaction to trigger the malicious request.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise through session hijacking, credential theft, and potential lateral movement within the network.

🟠

Likely Case

Session hijacking, credential theft, and unauthorized access to the affected device's administrative interface.

🟢

If Mitigated

Limited impact with proper input validation, output encoding, and security controls in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires social engineering to trick users into submitting malicious requests. The vulnerability itself is straightforward to exploit once the malicious request is crafted.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not publicly available

Restart Required: No

Instructions:

Check with ADB for firmware updates. If unavailable, implement workarounds and monitor for patches.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement server-side validation and sanitization of the Language parameter to reject malicious input.

Web Application Firewall (WAF)

all

Deploy a WAF with rules to block malicious JavaScript injection attempts in POST parameters.

🧯 If You Can't Patch

  • Restrict network access to the device's web interface using firewall rules or network segmentation.
  • Implement strong authentication mechanisms and monitor for unusual login attempts or parameter tampering.

🔍 How to Verify

Check if Vulnerable:

Test by submitting a POST request to /ui/login with a Language parameter containing JavaScript payload (e.g., <script>alert('test')</script>) and check if it executes.

Check Version:

Check firmware version via device web interface or administrative console.

Verify Fix Applied:

Retest with the same payload after applying fixes; ensure JavaScript does not execute and input is properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to /ui/login with JavaScript or HTML in parameters
  • Multiple failed login attempts with suspicious parameter values

Network Indicators:

  • HTTP traffic to /ui/login with encoded or obfuscated JavaScript in POST data

SIEM Query:

source="web_logs" AND uri_path="/ui/login" AND (http_method="POST") AND (param_value CONTAINS "<script>" OR param_value CONTAINS "javascript:")

🔗 References

📤 Share & Export