CVE-2024-42364
homepage DNS rebinding vulnerability (GHSL-2024-096)
In short
Homepage 0.9.1 lacks authentication and HTTPS by default, allowing attackers to trick users into visiting a malicious website that redirects to the internal Homepage instance via DNS rebinding, potentially exposing private data like API keys.
Technical detail
DNS rebinding vulnerability exploits Homepage's default lack of authentication and certificate validation. An attacker manipulates DNS responses to redirect the victim's browser from an external domain to the internal Homepage IP address, allowing unauthorized access to sensitive information. Successful exploitation requires the victim to visit the attacker-controlled website and the internal Homepage instance to be accessible without authentication.
Summary generated and translated by AI from the official description.
Homepage is a highly customizable homepage with Docker and service API integrations. The default setup of homepage 0.9.1 is vulnerable to DNS rebinding. Homepage is setup without certificate and authentication by default, leaving it to vulnerable to DNS rebinding. In this attack, an attacker will ask a user to visit his/her website. The attacker website will then change the DNS records of their domain from their IP address to the internal IP address of the homepage instance. To tell which IP addresses are valid, we can rebind a subdomain to each IP address we want to check, and see if there is a response. Once potential candidates have been found, the attacker can launch the attack by reading the response of the webserver after the IP address has changed. When the attacker domain is fetched, the response will be from the homepage instance, not the attacker website, because the IP address has been changed. Due to a lack of authentication, a user’s private information such as API keys (fixed after first report) and other private information can then be extracted by the attacker website.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N