ray /static/ get request method with sensitive query strings
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ray. It has been rated as problematic. This vulnerability affects unknown code of the file /static/. Performing a manipulation results in use of get request method with sensitive query strings. This vulnerability is identified as CVE-2023-6020. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, was found in ray (version unknown). This affects an unknown function of the file /static/. The manipulation with an unknown input leads to a use of get request method with sensitive query strings vulnerability. CWE is classifying the issue as CWE-598. The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. This is going to have an impact on confidentiality. The summary by CVE is:
LFI in Ray's /static/ directory allows attackers to read any file on the server without authentication.
The weakness was released 11/17/2023. The advisory is shared at huntr.com. This vulnerability is uniquely identified as CVE-2023-6020 since 11/08/2023. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.3
CNA Vector (huntr.dev): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Use of get request method with sensitive query stringsCWE: CWE-598
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/08/2023 🔍11/17/2023 🔍
11/17/2023 🔍
12/14/2023 🔍
Sources
Advisory: huntr.comStatus: Not defined
CVE: CVE-2023-6020 (🔍)
GCVE (CVE): GCVE-0-2023-6020
GCVE (VulDB): GCVE-100-245721
Entry
Created: 11/17/2023 07:47Updated: 12/14/2023 09:11
Changes: 11/17/2023 07:47 (44), 12/14/2023 09:11 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.