No data.
No data.
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-gx77-xgc2-4888 | Ray's New Token Authentication is Disabled By Default |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
No reference.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. At the request of the MITRE TL-Root and following the CVE Program’s Dispute Policy, it has been determined that this assignment did not identify a valid vulnerability based on the vendor's product security model. | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. At the request of the MITRE TL-Root and following the CVE Program’s Dispute Policy, it has been determined that this assignment did not identify a valid vulnerability based on the vendor's product security model. Additionally, this assignment conflicts with an existing CVE (CVE-2023-48022). |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-1188 | |
| References |
|
|
| Metrics |
cvssV4_0
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Anyscale Ray 2.52.0 contains an insecure default configuration in which token-based authentication for Ray management interfaces (including the dashboard and Jobs API) is disabled unless explicitly enabled by setting RAY_AUTH_MODE=token. In the default unauthenticated state, a remote attacker with network access to these interfaces can submit jobs and execute arbitrary code on the Ray cluster. NOTE: The vendor plans to enable token authentication by default in a future release. They recommend enabling token authentication to protect your cluster from unauthorized access. | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. At the request of the MITRE TL-Root and following the CVE Program’s Dispute Policy, it has been determined that this assignment did not identify a valid vulnerability based on the vendor's product security model. |
| Title | Anyscale Ray v2.52.0 Token Authentication Disabled by Default Insecure Configuration | |
| CPEs | ||
| Metrics |
cvssV4_0
|
cvssV4_0
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:anyscale:ray:2.52.0:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Anyscale
Anyscale ray |
|
| Vendors & Products |
Anyscale
Anyscale ray |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Anyscale Ray 2.52.0 contains an insecure default configuration in which token-based authentication for Ray management interfaces (including the dashboard and Jobs API) is disabled unless explicitly enabled by setting RAY_AUTH_MODE=token. In the default unauthenticated state, a remote attacker with network access to these interfaces can submit jobs and execute arbitrary code on the Ray cluster. NOTE: The vendor plans to enable token authentication by default in a future release. They recommend enabling token authentication to protect your cluster from unauthorized access. | |
| Title | Anyscale Ray v2.52.0 Token Authentication Disabled by Default Insecure Configuration | |
| Weaknesses | CWE-1188 | |
| References |
| |
| Metrics |
cvssV4_0
|
No weakness.