{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23470 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-23470 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23470 is a high-severity path traversal vulnerability in galaxyproject galaxy, published on 6 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23470 and fix it if it is affected.\n\nWhat it is: CVE-2022-23470 is a high-severity path traversal vulnerability in galaxyproject galaxy, published on 6 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-23470 in the wild and no public exploit code.\n\nAffected product: galaxyproject galaxy. 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-2022-23470/ (Markdown: https://insights.sbomify.com/CVE-2022-23470/index.md)","id":"CVE-2022-23470","markdown":"https://insights.sbomify.com/CVE-2022-23470/index.md","name":"CVE-2022-23470","record":{"aliases":["GHSA-grjf-2ghx-q77x"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Galaxy data analysis platform","requires_auth":"none","summary":"Attackers can read arbitrary files on the server due to improper static file handling in Galaxy's Gunicorn configuration.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"galaxy","vendor":"galaxyproject"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Galaxy is an open-source platform for data analysis. An arbitrary file read exists in Galaxy 22.01 and Galaxy 22.05 due to the switch to Gunicorn, which can be used to read any file accessible to the operating system user under which Galaxy is running. This vulnerability affects Galaxy 22.01 and higher, after the switch to gunicorn, which serve static contents directly.  Additionally, the vulnerability is mitigated when using Nginx or Apache to serve /static/* contents, instead of Galaxy's internal middleware. This issue has been patched in commit `e5e6bda4f` and will be included in future releases. Users are advised to manually patch their installations. There are no known workarounds for this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Arbitrary file access in the Galaxy data analysis platform","id":"CVE-2022-23470","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"containerd CRI stream server: Host memory exhaustion through terminal resize goroutine leak","id":"CVE-2022-23471"},"packages":[],"prev":{"headline":"Authorization header displayed in the debug logs","id":"CVE-2022-23469"},"products":["galaxy"],"published":"2022-12-06","related":[{"cvss_score":9.1,"headline":"Galaxy vulnerable to unauthorized modification of pages/visualizations due to insufficient permission check","id":"CVE-2023-27578","kev_date_added":null,"published":"2023-03-20"},{"cvss_score":7.6,"headline":"Stored Cross Site Scripting (Stored XSS) in Galaxy","id":"CVE-2024-42346","kev_date_added":null,"published":"2024-09-20"},{"cvss_score":6.5,"headline":"Possible Data Tampering \u0026 Loss of Public Datasets in Galaxy","id":"CVE-2024-42351","kev_date_added":null,"published":"2024-09-20"},{"cvss_score":6.3,"headline":"Galaxy vulnerable to Server Side Request Forgery during data imports","id":"CVE-2023-42812","kev_date_added":null,"published":"2023-09-22"},{"cvss_score":6.1,"headline":"Galaxy cross-site scripting (XSS)","id":"CVE-2018-1000516","kev_date_added":null,"published":"2018-06-26"},{"cvss_score":5.5,"headline":"galaxy-data-resource Command Line Template injection","id":"CVE-2015-10062","kev_date_added":null,"published":"2023-01-17"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["galaxyproject"]},"summary":"Attackers can read arbitrary files on the server due to improper static file handling in Galaxy's Gunicorn configuration.","url":"https://insights.sbomify.com/CVE-2022-23470/"}