A critical path traversal vulnerability in the Ray Dashboard allows unauthenticated remote attackers to perform local file disclosure, potentially exposing sensitive system information.

The Ray Dashboard (default port 8265) fails to properly validate and sanitize user-supplied paths within its static file handling mechanism. This allows unauthenticated remote attackers to utilize directory traversal sequences, such as ../, to bypass intended directory restrictions and read arbitrary files from the underlying server.

The ability to perform unauthorized local file disclosure presents a significant risk to the confidentiality of the affected environment. An attacker could retrieve sensitive configuration files, environment variables, or credentials stored on the server, which may facilitate further compromise, unauthorized access to connected systems, or lateral movement within the network. Given the CVSS score of 7.5, this vulnerability is considered high severity, as it provides a clear path for data exfiltration without requiring any authentication.

Immediate Action: Update the Ray installation to version 2.8.1 or later immediately to incorporate the necessary path sanitization fixes.

Proactive Monitoring: Review web server and application access logs for suspicious patterns, specifically looking for repeated directory traversal sequences (e.g., ../) targeting the Ray Dashboard port 8265.

Compensating Controls: Deploy a Web Application Firewall (WAF) rule to block requests containing directory traversal sequences directed at the Ray Dashboard interface until the patch can be applied.

Public Exploit Available: Yes, a published proof-of-concept exists as referenced by Packet Storm Security.

Given the availability of a public proof-of-concept and the ease of exploitation, this vulnerability poses an immediate threat to the integrity and confidentiality of systems running the Ray Dashboard. Administrators must prioritize updating to version 2.8.1 or higher to eliminate the attack vector. If patching is not immediately feasible, ensure that access to the Ray Dashboard is restricted to trusted internal networks and protected by additional authentication layers.