CVE-2023-48023
📋 TL;DR
CVE-2023-48023 is a Server-Side Request Forgery (SSRF) vulnerability in the /log_proxy endpoint of Anyscale Ray versions 2.6.3 and 2.8.0. This allows attackers to make unauthorized requests from the Ray server to internal network resources. Organizations using these Ray versions in any network environment are affected, though the vendor notes Ray is intended for controlled networks only.
💻 Affected Systems
- Anyscale Ray
📦 What is this software?
Ray by Anyscale
Ray by Anyscale
⚠️ Risk & Real-World Impact
Worst Case
Attackers could access sensitive internal services, exfiltrate data, or pivot to other systems within the network.
Likely Case
Unauthorized access to internal HTTP/HTTPS services, potentially exposing metadata or limited internal resources.
If Mitigated
Minimal impact if network segmentation and proper access controls prevent internal service access.
🎯 Exploit Status
Exploitation requires network access to the Ray instance. Public technical details are available from Bishop Fox.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Versions after 2.8.0 (check latest releases)
Vendor Advisory: https://docs.ray.io/en/latest/ray-security/index.html
Restart Required: Yes
Instructions:
1. Upgrade Ray to the latest version. 2. Restart all Ray services. 3. Verify the /log_proxy endpoint is no longer vulnerable.
🔧 Temporary Workarounds
Network Segmentation
allRestrict network access to Ray instances and block outbound requests from Ray to internal services.
Disable /log_proxy Endpoint
linuxIf not needed, disable or block access to the /log_proxy endpoint via firewall or configuration.
# Use firewall rules to block /log_proxy
# Example for iptables: iptables -A INPUT -p tcp --dport [RAY_PORT] -m string --string "/log_proxy" --algo bm -j DROP
🧯 If You Can't Patch
- Implement strict network segmentation to isolate Ray instances from sensitive internal services.
- Deploy web application firewalls (WAF) or reverse proxies to filter malicious requests to the /log_proxy endpoint.
🔍 How to Verify
Check if Vulnerable:
Check if Ray version is 2.6.3 or 2.8.0 and test if /log_proxy endpoint accepts external URLs.Check Version:
ray --versionVerify Fix Applied:
After patching, test that /log_proxy no longer processes requests to internal or external URLs.📡 Detection & Monitoring
Log Indicators:
- Unusual requests to /log_proxy endpoint with external or internal IPs in logs.
Network Indicators:
- Outbound HTTP/HTTPS requests from Ray server to unexpected internal destinations.
SIEM Query:
source="ray_logs" AND url_path="/log_proxy" AND (dest_ip!=local_network OR dest_ip=external_ip)