ray vulnerable to Insertion of Sensitive Information into Log File
CVE-2025-1979 · GHSA-w4rh-fgx7-q63m · published 2025-03-06 · updated 2025-04-09
- Severity
- Medium
- CVSS score
- 6.4
- Chance of exploitation (EPSS)
- 0.19%
- Fixed in
- 2.43.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
Versions of the package ray before 2.43.0 are vulnerable to Insertion of Sensitive Information into Log File where the redis password is being logged in the standard logging. If the redis password is passed as an argument, it will be logged and could potentially leak the password.
Upgrade ray to 2.43.0 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| ray | PyPI | < 2.43.0 | 2.43.0 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- Highn8n: Shared Credential Header Leak via HTTP Request Pagination Expressionn8n, n8n, n8n
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalRay's New Token Authentication is Disabled By Defaultray
- CriticalRay has arbitrary code execution via jobs submission APIray
- CriticalRay Path Traversal vulnerabilityray
- CriticalRay Missing Authorization vulnerabilityray
- CriticalRay OS Command Injection vulnerabilityray
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.