opengeos streamlit-geospatial up to 115/126 10_????_Earth_Engine_Datasets.py eval vis_params input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as very critical has been reported in opengeos streamlit-geospatial up to 115/126. Affected is the function eval of the file pages/10_????_Earth_Engine_Datasets.py. Performing a manipulation of the argument vis_params results in input validation.
This vulnerability is known as CVE-2024-41117. Remote exploitation of the attack is possible. No exploit is available.
It is recommended to apply a patch to fix this issue.
Details
A vulnerability was found in opengeos streamlit-geospatial up to 115/126. It has been classified as very critical. This affects the function eval of the file pages/10_????_Earth_Engine_Datasets.py. The manipulation of the argument vis_params with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
streamlit-geospatial is a streamlit multipage app for geospatial applications. Prior to commit c4f81d9616d40c60584e36abb15300853a66e489, the `vis_params` variable on line 115 in `pages/10_????_Earth_Engine_Datasets.py` takes user input, which is later used in the `eval()` function on line 126, leading to remote code execution. Commit c4f81d9616d40c60584e36abb15300853a66e489 fixes this issue.
It is possible to read the advisory at securitylab.github.com. This vulnerability is uniquely identified as CVE-2024-41117 since 07/15/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/26/2024).
Applying the patch c4f81d9616d40c60584e36abb15300853a66e489 is able to eliminate this problem.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.7
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 9.8
CNA Vector (GitHub_M): 🔍
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: Input validationCWE: CWE-20
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: c4f81d9616d40c60584e36abb15300853a66e489
Timeline
07/15/2024 🔍07/26/2024 🔍
07/26/2024 🔍
08/26/2024 🔍
Sources
Advisory: GHSL-2024-100Status: Confirmed
CVE: CVE-2024-41117 (🔍)
GCVE (CVE): GCVE-0-2024-41117
GCVE (VulDB): GCVE-100-272535
Entry
Created: 07/26/2024 23:08Updated: 08/26/2024 23:21
Changes: 07/26/2024 23:08 (66), 07/30/2024 12:01 (1), 08/26/2024 23:21 (11)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.