CVE-2023-6020 is a local file inclusion (LFI) vulnerability in the Ray open source project's /static/ directory. The flaw is due to missing authorization checks (CWE-862), allowing unauthenticated attackers to read arbitrary files on the server. The vulnerability affects all Ray versions prior to 2.8.1 and is exploitable remotely without user interaction or authentication. The issue was reported via huntr.dev, and a public exploit is available.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit auxiliary module targeting CVE-2023-6020, a local file inclusion (LFI) vulnerability in Ray (prior to version 2.8.1, specifically up to 2.6.3). The module is written in Ruby and leverages the Metasploit framework's HTTP client capabilities. It works by sending a crafted HTTP GET request to the Ray server's web interface (default port 8265), exploiting a path traversal flaw in the '/static/js/' endpoint to read arbitrary files from the server's filesystem. The module first checks the Ray version via the '/api/version' endpoint, then attempts to read the specified file (default: '/etc/passwd'). The exploit is operational and provides file read capabilities but does not provide a shell or code execution. The only file in the repository is the Metasploit module itself, and it is structured according to standard Metasploit conventions.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.