Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilityinternet-exposed-servicewidely-deployed-product-advisorycredential-stealer-activity

Browser 0.0.0.0 Flaw Exposed Local Ray and Selenium Services to RCE and Cryptomining

Vulnerability Disclosure · 4 sources · Updated 4mo ago · First seen Aug 13, 2024

Browser 0.0.0.0 Flaw Exposed Local Ray and Selenium Services to RCE and Cryptomining

Researchers disclosed a browser networking flaw dubbed 0.0.0.0 Day that allows malicious websites to send HTTP requests to services bound to localhost by targeting 0.0.0.0, bypassing expected browser protections on macOS and Linux. The issue affects major browsers through inconsistent handling of localhost and private network requests, enabling state-changing actions and, in some cases, remote code execution against local services even when attackers cannot read responses because of CORS. Apple, Google, and other browser vendors have acknowledged the problem and moved to block or restrict 0.0.0.0 as a destination, while Windows is largely unaffected because the operating system already blocks such traffic.

The flaw was tied to active exploitation campaigns against AI and automation infrastructure, including ShadowRay attacks on publicly exposed Ray clusters via the Ray Dashboard and Jobs API, as well as attacks on Selenium Grid and PyTorch/TorchServe instances. Oligo reported hundreds to thousands of compromised Ray servers, with attackers stealing cloud and SaaS credentials, exposing private keys, establishing reverse shells, and deploying cryptominers such as XMRig and NBMiner; Wiz separately documented SeleniumGreed, in which exposed Selenium Grid services were abused for cryptomining. Defenders were urged to stop exposing Ray dashboards and Selenium services to the internet, add authentication and authorization layers, enforce network isolation and firewalling, and harden local services with CSRF protections, host validation, HTTPS, and browser-related private network controls.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events · Mar 26, 2024 – Aug 13, 2024
  1. Aug 13, 20242y ago

    CSIRT.SK highlights 0.0.0.0 Day and notes long-known weakness

    CSIRT.SK published an advisory on the 0.0.0.0 Day issue, stating the underlying weakness had been known since 2006 and summarizing observed exploitation against localhost and local-network services in browsers on macOS and Linux.

    18 rokov stará zraniteľnosť „0.0.0.0“ | CSIRT.SK
  2. Aug 7, 20242y ago

    Oligo discloses browser flaw dubbed 0.0.0.0 Day

    Oligo disclosed "0.0.0.0 Day," a browser logic flaw that lets public websites send requests to localhost-bound services via 0.0.0.0, bypassing expected protections. The company said the issue was being actively exploited, including in ShadowRay-style attacks and against services such as Selenium Grid and TorchServe.

    0.0.0.0 Day: Exploiting Localhost APIs From the Browser | Oligo Security
  3. Jul 25, 20242y ago

    Wiz reports SeleniumGreed cryptomining attacks on Selenium Grid

    Wiz published details of "SeleniumGreed," describing threat actors exploiting exposed Selenium Grid services for cryptomining and providing attack-flow and remediation guidance. The report tied Selenium Grid abuse to the broader pattern of attacks against locally or publicly exposed developer and AI services.

    SeleniumGreed: Threat actors exploit exposed Selenium Grid services for Cryptomining
  4. Mar 26, 20243y ago

    Oligo discloses ShadowRay active exploitation campaign

    On its publication date, Oligo publicly disclosed the "ShadowRay" campaign targeting AI workloads, describing active in-the-wild exploitation of exposed Ray clusters and warning that hundreds to thousands of servers had been compromised globally.

    ShadowRay: First Known Attack Campaign Targeting AI Workloads Exploited In The Wild | Oligo Security
  5. Mar 26, 20243y ago

    ShadowRay exploitation of exposed Ray clusters begins

    Oligo reported evidence that attackers had been exploiting publicly exposed Ray clusters for at least seven months before its March 2024 publication, abusing the Ray Jobs API via the dashboard to achieve remote code execution. The campaign led to widespread compromise, credential theft, and cryptomining on affected servers.

    ShadowRay: First Known Attack Campaign Targeting AI Workloads Exploited In The Wild | Oligo Security
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Affected products

9 linked
Selenium GridSafariTorchserveFirefoxMacosChromiumChromiumRayLinux

Organizations

3 linked
MozillaAppleGoogle

Observables

1 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.