An 18-year-old bug, dubbed “0.0.0.0 Day,” allows malicious websites to bypass security in Chrome, Firefox, and Safari to breach local networks. <\/gwmw><\/h2>\n\n\n\nOligo Security’s research team\u00a0warns of an 18-year-old bug, dubbed “0.0.0.0 Day,” that allows malicious websites to bypass security in Chrome, Firefox, and Safari to breach local networks. <\/p>\n\n\n\n
The issue potentially leads to unauthorized access and remote code\u00a0execution on local services by attackers outside the network.<\/p>\n\n\n\n
“The issue stems from the inconsistent implementation of security mechanisms across different browsers, along with a lack of standardization in the browser industry.” reads the advisory<\/strong><\/a> published by Oligo Security’s. “As a result, the seemingly innocuous IP address, 0.0.0.0, can become a powerful tool for attackers to exploit local services, including those used for development, operating systems, and even internal networks.”<\/em><\/p>\n\n\n\n
“It is worth noting that the percentage of websites that communicate 0.0.0.0 is on the rise, based on counters in Chromium.\u00a0Those pages could be malicious<\/a>, and currently the percentage stands at 0.015% of all websites.” continues the report. “With 200 million websites in the world as of August 2024, as many as ~100K<\/strong>\u00a0public websites may be communicating with 0.0.0.0.\u00a0 The figure below illustrates this rise.”<\/em><\/p>\n\n\n
\n![\"0.0.0.0](\"https:\/\/i0.wp.com\/securityaffairs.com\/wp-content\/uploads\/2024\/08\/image-6.png?resize=1024%2C486&ssl=1\")
<\/a><\/figure><\/div>\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.
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>
Follow me on Twitter: @securityaffairs<\/strong><\/a> and Facebook<\/strong><\/a> and Mastodon<\/a><\/p>\n\n\n\n
Pierluigi Paganini<\/strong><\/a><\/p>\n\n\n\n
(<\/strong>SecurityAffairs<\/strong><\/a>\u00a0\u2013<\/strong>\u00a0hacking, 0.0.0.0 Day)<\/strong><\/gwmw><\/p>\n","protected":false},"excerpt":{"rendered":"
Oligo Security’s research team\u00a0warns of an 18-year-old bug, dubbed “0.0.0.0 Day,” that allows malicious websites to bypass security in Chrome, Firefox, and Safari to breach local networks. <\/p>\n\n\n\n
The issue potentially leads to unauthorized access and remote code\u00a0execution on local services by attackers outside the network.<\/p>\n\n\n\n
“The issue stems from the inconsistent implementation of security mechanisms across different browsers, along with a lack of standardization in the browser industry.” reads the advisory<\/strong><\/a> published by Oligo Security’s. “As a result, the seemingly innocuous IP address, 0.0.0.0, can become a powerful tool for attackers to exploit local services, including those used for development, operating systems, and even internal networks.”<\/em><\/p>\n\n\n\n
“It is worth noting that the percentage of websites that communicate 0.0.0.0 is on the rise, based on counters in Chromium.\u00a0Those pages could be malicious<\/a>, and currently the percentage stands at 0.015% of all websites.” continues the report. “With 200 million websites in the world as of August 2024, as many as ~100K<\/strong>\u00a0public websites may be communicating with 0.0.0.0.\u00a0 The figure below illustrates this rise.”<\/em><\/p>\n\n\n
![\"0.0.0.0](\"https:\/\/i0.wp.com\/securityaffairs.com\/wp-content\/uploads\/2024\/08\/image-6.png?ssl=1\")
<\/a><\/figure><\/div>\n\n\nThe 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.
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>
Follow me on Twitter: @securityaffairs<\/strong><\/a> and Facebook<\/strong><\/a> and Mastodon<\/a><\/p>\n\n\n\n
Pierluigi Paganini<\/strong><\/a><\/p>\n\n\n\n
(<\/strong>SecurityAffairs<\/strong><\/a>\u00a0\u2013<\/strong>\u00a0hacking, 0.0.0.0 Day)<\/strong>