{"answers":{"affected":"3 open source packages ship an affected version, including mage-ai. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45189 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45189 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45189 is a medium-severity path traversal vulnerability in mage:mage-ai, published on 23 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45189 and fix it if it is affected.\n\nWhat it is: CVE-2024-45189 is a medium-severity path traversal vulnerability in mage:mage-ai, published on 23 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-45189 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mage-ai (PyPI): affected all versions up to 0.9.73; no fix listed\n- mage-ai (PyPI): affected all versions up to 0.9.73; no fix listed\n- mage-ai (PyPI): affected all versions up to 0.9.73; no fix listed\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-45189/ (Markdown: https://insights.sbomify.com/CVE-2024-45189/index.md)","id":"CVE-2024-45189","markdown":"https://insights.sbomify.com/CVE-2024-45189/index.md","name":"CVE-2024-45189","record":{"aliases":["GHSA-cgxv-795x-3vqr","PYSEC-2026-1599"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mage AI data platform","requires_auth":"low_privilege","summary":"Remote attackers with Viewer role can leak arbitrary files from the Mage server via path traversal in Git Content requests.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"JFROG","cpe":[{"product":"mage-ai","vendor":"mage"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Mage AI allows remote users with the \"Viewer\" role to leak arbitrary files from the Mage server due to a path traversal in the \"Git Content\" request","ecosystems":["PyPI"],"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":"Mage AI git content request remote arbitrary file leak","id":"CVE-2024-45189","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Mage AI pipeline interaction request remote arbitrary file leak","id":"CVE-2024-45190"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.9.73"],"package":"mage-ai","purl":null,"source":"GHSA-cgxv-795x-3vqr"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.9.73"],"package":"mage-ai","purl":"pkg:pypi/mage-ai","source":"GHSA-cgxv-795x-3vqr"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.9.73"],"package":"mage-ai","purl":"pkg:pypi/mage-ai","source":"PYSEC-2026-1599"}],"prev":{"headline":"Mage AI file content request remote arbitrary file leak","id":"CVE-2024-45188"},"products":["mage:mage-ai"],"published":"2024-08-23","related":[{"cvss_score":7.1,"headline":"Mage AI allows deleted users to use the terminal server with admin access, leading to remote code execution","id":"CVE-2024-45187","kev_date_added":null,"published":"2024-08-23"},{"cvss_score":6.5,"headline":"Mage AI file content request remote arbitrary file leak","id":"CVE-2024-45188","kev_date_added":null,"published":"2024-08-23"},{"cvss_score":6.5,"headline":"Mage AI pipeline interaction request remote arbitrary file leak","id":"CVE-2024-45190","kev_date_added":null,"published":"2024-08-23"},{"cvss_score":5.9,"headline":"Mage terminal user authentication not working properly","id":"CVE-2023-31143","kev_date_added":null,"published":"2023-05-09"},{"cvss_score":5.3,"headline":"Mage AI allows remote unauthenticated attackers to leak the terminal server command history of arbitrary users","id":"CVE-2024-8072","kev_date_added":null,"published":"2024-08-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-25","vendors":["mage"]},"summary":"Remote attackers with Viewer role can leak arbitrary files from the Mage server via path traversal in Git Content requests.","url":"https://insights.sbomify.com/CVE-2024-45189/"}