<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ray Project - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/ray-project/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 11 Aug 2026 14:06:04 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/ray-project/feed.xml" rel="self" type="application/rss+xml"/><item><title>Directory Traversal and LFI in Ray 2.56.0</title><link>https://feed.craftedsignal.io/briefs/2026-08-ray-traversal/</link><pubDate>Tue, 11 Aug 2026 14:06:04 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-ray-traversal/</guid><description>Ray 2.56.0 contains a directory traversal and local file inclusion vulnerability in the /api/v0/logs endpoint allowing unauthenticated attackers to read arbitrary files.</description><content:encoded><![CDATA[<p>Ray version 2.56.0 contains a critical directory traversal and local file inclusion vulnerability within the /api/v0/logs API endpoint. The vulnerability allows an unauthenticated remote attacker to access files outside the intended log directory by supplying a crafted glob filter via the 'glob' parameter. An attacker must possess a valid node_id to interact with the API successfully. This vulnerability has been documented with a functional proof-of-concept exploit which demonstrates the ability to read sensitive files from the underlying host filesystem, such as those within /etc. Ray maintainers have been notified, and a fix is currently under review in GitHub Pull Request 64701.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker performs reconnaissance to identify Ray dashboard instances accessible over the network, typically on port 6379.</li>
<li>Attacker probes the environment to enumerate or discover a valid node_id required for interaction with the /api/v0/logs endpoint.</li>
<li>Attacker crafts an HTTP GET request to the /api/v0/logs endpoint.</li>
<li>Attacker includes the 'node_id' parameter with the discovered identifier.</li>
<li>Attacker injects a malicious traversal payload into the 'glob' parameter, such as '../../../../etc/*'.</li>
<li>The Ray API processes the glob pattern without sufficient validation, concatenating the malicious path.</li>
<li>The application returns the contents of the requested file or directory within the HTTP response body.</li>
<li>Attacker successfully exfiltrates sensitive files from the server's filesystem.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated remote attackers to read arbitrary files on the system running Ray, potentially leading to the exposure of credentials, configuration files, or other sensitive system data. The vulnerability is confirmed to affect Ubuntu 22.04 and RHEL 10.0 deployments.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Implement network access controls to restrict access to the Ray dashboard (default port 6379) to authorized internal networks only.</li>
<li>Monitor webserver logs for HTTP GET requests to '/api/v0/logs' containing directory traversal characters (e.g., '../') in the 'glob' parameter.</li>
<li>Deploy the Sigma rule provided in this brief to identify exploitation attempts against the logs API.</li>
<li>Apply the vendor-provided patch once released via the official Ray project repository (GH PR 64701).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>webapps</category><category>directory-traversal</category><category>lfi</category></item></channel></rss>