<\/a><\/figure><\/div>\n\n\n<\/gwmw>The ‘0.0.0.0 Day’ vulnerability reveals a critical flaw in how browsers manage network requests, potentially allowing malicious actors to access sensitive services on local devices.<\/gwmw><\/p>\n\n\n\n
The vulnerability does not impact Windows devices because the IP address is unreachable.<\/p>\n\n\n\n
The experts noticed that public websites (like .com domains) can communicate with services running on the local network (localhost) and potentially execute arbitrary code on the visitor\u2019s host by using the address 0.0.0.0 instead of localhost\/127.0.0.1.\u00a0<\/p>\n\n\n\n
PNA (Private Network Access) is an initiative led by Google, and continues to evolve and improve.\u00a0 The experts pointed out that the 0.0.0.0 Day flaw also bypassed the PNA (Private Network Access) mechanism developed by Google in Chromium to block websites from accessing 127.0.0.1, localhost, and other private IPs via Javascript when loaded from public websites.<\/p>\n\n\n\n
The flaw also bypassed Cross Origin Resource Sharing (CORS) mechanism for integrating applications. CORS defines a way for client web applications that are loaded in one domain to interact with resources in a different domain.<\/p>\n\n\n\n
Recent attacks, like those from SeleniumGreed, have exploited Selenium Grid public servers to gain initial access to organizations by using known Remote Code Execution (RCE) vulnerabilities. The experts discovered that was possible to remotely execute arbitrary code on local Selenium Grid instances by sending a crafted POST request to http:\/\/0.0.0.0:4444\/.<\/p>\n\n\n\n
Another attack vector observed by the experts uses a local Selenium Grid cluster to browse websites with insecure browser configurations, potentially allowing access to internal domains and private DNS records behind a VPN.<\/gwmw><\/p>\n\n\n\n
The researchers shared their findings with web browser development teams in April 2024, and they expect that the issue will be completely addressed.<\/p>\n\n\n\n
“Thanks to our reports, browsers prioritized those fixes and made breaking changes, blocking 0.0.0.0 as target IP. It was important to have a collaborative fix to avoid a situation in which browsers would \u201czero-day each other\u201d by introducing a fix.” concludes the report.<\/em><\/gwmw><\/p>\n\n\n\n