{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2617 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2617 is a high-severity vulnerability in [UNKNOWN] hawtio, published on 22 May 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-2617 and fix it if it is affected.\n\nWhat it is: CVE-2017-2617 is a high-severity vulnerability in [UNKNOWN] hawtio, published on 22 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-2617 in the wild and no public exploit code.\n\nAffected product: [UNKNOWN] hawtio. 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-2617/ (Markdown: https://insights.sbomify.com/CVE-2017-2617/index.md)","id":"CVE-2017-2617","markdown":"https://insights.sbomify.com/CVE-2017-2617/index.md","name":"CVE-2017-2617","record":{"aliases":["GHSA-3pgx-46rx-xc9j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java monitoring console","requires_auth":"low_privilege","summary":"An attacker can achieve remote code execution by uploading a crafted file to the hawtio monitoring console.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"hawtio","vendor":"hawt"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H","version":"3.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"hawtio before version 1.5.5 is vulnerable to remote code execution via file upload. An attacker could use this vulnerability to upload a crafted file which could be executed on a target machine where hawtio is deployed.","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":"File upload in hawtio","id":"CVE-2017-2617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Null dereference in kernel","id":"CVE-2017-2618"},"packages":[],"prev":{"headline":"Race condition in util-linux","id":"CVE-2017-2616"},"products":["hawtio"],"published":"2018-05-22","related":[{"cvss_score":9.8,"headline":"Server-Side Request Forgery in Hawt Hawtio","id":"CVE-2019-9827","kev_date_added":null,"published":"2019-07-03"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2014-0121","kev_date_added":null,"published":"2017-12-29"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2014-0120","kev_date_added":null,"published":"2017-12-29"},{"cvss_score":8.8,"headline":"Cross-Site Request Forgery in hawtio","id":"CVE-2017-7556","kev_date_added":null,"published":"2017-08-17"},{"cvss_score":8.7,"headline":"Insecure cookie sharing in Hawtio","id":"CVE-2017-2589","kev_date_added":null,"published":"2018-07-26"},{"cvss_score":5.5,"headline":"hawtio vulnerable to Path Traversal","id":"CVE-2023-33544","kev_date_added":null,"published":"2023-06-01"}],"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":["[UNKNOWN]"]},"summary":"An attacker can achieve remote code execution by uploading a crafted file to the hawtio monitoring console.","url":"https://insights.sbomify.com/CVE-2017-2617/"}