LG SuperSign Media Editor ContentRestController getObject Directory Traversal Information Disclosure Vulnerability

The core of this vulnerability lies within the getObject method of the ContentRestController class. Due to a lack of proper input validation on user-supplied file paths, an attacker can craft malicious requests to access files outside of the intended directory. This could lead to the exposure of configuration files, source code, or other sensitive data stored on the system. The lack of authentication required to exploit this vulnerability significantly broadens the potential attack surface, making it accessible to a wide range of threat actors. Successful exploitation could result in significant data breaches and compromise the integrity of the media editing system.

Organizations utilizing LG SuperSign Media Editor for digital signage and media management are at risk, particularly those with older, unpatched installations. Shared hosting environments where multiple users share the same server instance are also at increased risk, as a compromise of one user's account could potentially lead to the disclosure of data belonging to other users.

• linux / server:

journalctl -u LGSuperSignMediaEditor | grep -i "directory traversal"

• generic web:

curl -I 'http://<target>/ContentRestController/getObject?path=../../../../etc/passwd'  # Check for 200 OK and sensitive file content in headers

1. 2024-05-03Disclosure

   disclosure

1. Reserviert2023-08-14
2. Veröffentlicht2024-05-03
3. Geändert2024-08-02
4. EPSS aktualisiert2026-04-02

Since a patch is not yet available, immediate mitigation steps are crucial. Implementing a Web Application Firewall (WAF) with rules to filter out malicious path traversal attempts is a primary defense. Specifically, WAF rules should be configured to block requests containing directory traversal sequences like ../ or encoded equivalents. Additionally, restricting access to the Media Editor service and implementing strict file permissions can limit the potential damage. Regularly review and audit file access logs for suspicious activity. After implementing WAF rules, verify their effectiveness by attempting to access files outside the intended directory.