{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5244 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5244 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5244 is a low-severity vulnerability in Rapid7 Metasploit (Pro, Express, and Community editions), published on 15 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-5244 and fix it if it is affected.\n\nWhat it is: CVE-2017-5244 is a low-severity vulnerability in Rapid7 Metasploit (Pro, Express, and Community editions), published on 15 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-5244 in the wild and no public exploit code.\n\nAffected product: Rapid7 Metasploit (Pro, Express, and Community editions). 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-5244/ (Markdown: https://insights.sbomify.com/CVE-2017-5244/index.md)","id":"CVE-2017-5244","markdown":"https://insights.sbomify.com/CVE-2017-5244/index.md","name":"CVE-2017-5244","record":{"aliases":["GHSA-7vfm-4xqj-pv85"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Metasploit Framework","requires_auth":"low_privilege","summary":"An attacker can stop running Metasploit tasks by tricking an authenticated user into visiting a malicious page, causing service disruption.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"metasploit","vendor":"rapid7"}],"cvss":{"score":3.5,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Routes used to stop running Metasploit tasks (either particular ones or all tasks) allowed GET requests. Only POST requests should have been allowed, as the stop/stop_all routes change the state of the service. This could have allowed an attacker to stop currently-running Metasploit tasks by getting an authenticated user to execute JavaScript. As of Metasploit 4.14.0 (Update 2017061301), the routes for stopping tasks only allow POST requests, which validate the presence of a secret token to prevent CSRF attacks.","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":"Cross-site request forgery in Metasploit (Pro, Express, and Community editions)","id":"CVE-2017-5244","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2017-5245"},"packages":[],"prev":{"headline":"Weak cryptography in Nexpose hardware appliance","id":"CVE-2017-5243"},"products":["Metasploit (Pro, Express, and Community editions)"],"published":"2017-06-15","related":[{"cvss_score":8.1,"headline":"Metasploit Framework 'drb_remote_codeexec' code execution","id":"CVE-2020-7385","kev_date_added":null,"published":"2021-04-23"},{"cvss_score":8.1,"headline":"Rapid7 Metasploit Framework Relative Path Traversal in telpho10_credential_dump module","id":"CVE-2020-7377","kev_date_added":null,"published":"2020-08-24"},{"cvss_score":7.8,"headline":"Other in Metasploit Pro","id":"CVE-2017-5235","kev_date_added":null,"published":"2017-03-02"},{"cvss_score":7.5,"headline":"Rapid7 Metasploit HTTP Handler Denial of Service","id":"CVE-2019-5645","kev_date_added":null,"published":"2020-09-01"},{"cvss_score":7.4,"headline":"Rapid7 Metasploit Framework Zip Import Directory Traversal","id":"CVE-2019-5624","kev_date_added":null,"published":"2019-04-30"},{"cvss_score":7.1,"headline":"Rapid7 Metasploit Framework Relative Path Traversal in enum_osx module","id":"CVE-2020-7376","kev_date_added":null,"published":"2020-08-24"},{"cvss_score":7.1,"headline":"Path traversal in Metasploit","id":"CVE-2017-5228","kev_date_added":null,"published":"2017-03-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":["Rapid7"]},"summary":"An attacker can stop running Metasploit tasks by tricking an authenticated user into visiting a malicious page, causing service disruption.","url":"https://insights.sbomify.com/CVE-2017-5244/"}