{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5219 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5219 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5219 is a critical path traversal vulnerability in n/a, published on 2 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-5219 and fix it if it is affected.\n\nWhat it is: CVE-2017-5219 is a critical path traversal vulnerability in n/a, published on 2 Feb 2017. 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-2017-5219 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2017-5219/ (Markdown: https://insights.sbomify.com/CVE-2017-5219/index.md)","id":"CVE-2017-5219","markdown":"https://insights.sbomify.com/CVE-2017-5219/index.md","name":"CVE-2017-5219","record":{"aliases":["GHSA-9h7v-mvfw-jj5x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"SageCRM","requires_auth":"none","summary":"Attackers can upload a crafted zip file to traverse directories and install a web shell, achieving remote code execution with SYSTEM privileges.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sagecrm","vendor":"sagecrm"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An issue was discovered in SageCRM 7.x before 7.3 SP3. The Component Manager functionality, provided by SageCRM, permits additional components to be added to the application to enhance provided functionality. This functionality allows a zip file to be uploaded, containing a valid .ecf component file, which will be extracted to the inf directory outside of the webroot. By creating a zip file containing an empty .ecf file, to pass file-validation checks, any other file provided in zip file will be extracted onto the filesystem. In this case, a web shell with the filename '..\\WWWRoot\\CustomPages\\aspshell.asp' was included within the zip file that, when extracted, traversed back out of the inf directory and into the SageCRM webroot. This permitted remote interaction with the underlying filesystem with the highest privilege level, SYSTEM.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2017-5219","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Local file disclosure in PHPMailer","id":"CVE-2017-5223"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2017-5218"},"products":["n/a"],"published":"2017-02-02","related":[{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2017-5218","kev_date_added":null,"published":"2017-02-02"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can upload a crafted zip file to traverse directories and install a web shell, achieving remote code execution with SYSTEM privileges.","url":"https://insights.sbomify.com/CVE-2017-5219/"}