{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41113 exists.","fix":"No fix has been published for CVE-2024-41113 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-41113 is a critical code injection vulnerability in opengeos streamlit-geospatial, published on 26 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-41113 and fix it if it is affected.\n\nWhat it is: CVE-2024-41113 is a critical code injection vulnerability in opengeos streamlit-geospatial, published on 26 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41113 exists.\n\nAffected product: opengeos streamlit-geospatial. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-41113/ (Markdown: https://insights.sbomify.com/CVE-2024-41113/index.md)","id":"CVE-2024-41113","markdown":"https://insights.sbomify.com/CVE-2024-41113/index.md","name":"CVE-2024-41113","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Streamlit geospatial app","requires_auth":"none","summary":"Attackers can execute arbitrary code via the vis_params input in the Timelapse page due to unsafe eval usage.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"streamlit-geospatial","vendor":"opengeos"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"streamlit-geospatial is a streamlit multipage app for geospatial applications. Prior to commit c4f81d9616d40c60584e36abb15300853a66e489, the `vis_params` variable on line 383 or line 390 in `pages/1_📷_Timelapse.py` takes user input, which is later used in the `eval()` function on line 395, leading to remote code execution. Commit c4f81d9616d40c60584e36abb15300853a66e489 fixes this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Code injection in streamlit-geospatial","id":"CVE-2024-41113","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":0,"n_references":5,"next":{"headline":"Code injection in streamlit-geospatial","id":"CVE-2024-41114"},"packages":[],"prev":{"headline":"Remote code execution in streamlit geospatial in pages/1_📷_Timelapse.py Any Earth Engine ImageCollection option palette","id":"CVE-2024-41112"},"products":["streamlit-geospatial"],"published":"2024-07-26","related":[{"cvss_score":9.8,"headline":"Remote code execution in streamlit geospatial in pages/1_📷_Timelapse.py Any Earth Engine ImageCollection option palette","id":"CVE-2024-41112","kev_date_added":null,"published":"2024-07-26"},{"cvss_score":9.8,"headline":"Code injection in streamlit-geospatial","id":"CVE-2024-41114","kev_date_added":null,"published":"2024-07-26"},{"cvss_score":9.8,"headline":"Remote code execution in streamlit geospatial in pages/1_📷_Timelapse.py MODIS Ocean Color SMI option palette","id":"CVE-2024-41115","kev_date_added":null,"published":"2024-07-26"},{"cvss_score":9.8,"headline":"Remote code execution in streamlit geospatial in pages/1_📷_Timelapse.py MODIS Ocean Color SMI option vis_params","id":"CVE-2024-41116","kev_date_added":null,"published":"2024-07-26"},{"cvss_score":9.8,"headline":"Remote code execution in streamlit geospatial in pages/10_🌍_Earth_Engine_Datasets.py","id":"CVE-2024-41117","kev_date_added":null,"published":"2024-07-26"},{"cvss_score":9.8,"headline":"streamlit-geospatial remote code execution in pages/8_🏜️_Raster_Data_Visualization.py","id":"CVE-2024-41119","kev_date_added":null,"published":"2024-07-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["opengeos"]},"summary":"Attackers can execute arbitrary code via the vis_params input in the Timelapse page due to unsafe eval usage.","url":"https://insights.sbomify.com/CVE-2024-41113/"}