Low severity3.5NVD Advisory· Published Jun 15, 2017· Updated Jun 17, 2026
CVE-2017-5244
CVE-2017-5244
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
3cpe:2.3:a:rapid7:metasploit:*:*:*:*:*:*:*:*+ 1 more
- cpe:2.3:a:rapid7:metasploit:*:*:*:*:*:*:*:*range: <=4.13.19
- (no CPE)range: <4.14.0 (Update 2017061301)
- Rapid7/Metasploit (Pro, Express, and Community editions)v5Range: < 4.14.0 (Update 2017061301)
Patches
Vulnerability mechanics
References
3- community.rapid7.com/community/metasploit/blog/2017/06/15/r7-2017-16-cve-2017-5244-lack-of-csrf-protection-for-stopping-tasks-in-metasploit-pro-express-and-community-editions-fixednvdExploitVDB EntryVendor Advisory
- www.securityfocus.com/bid/99082nvdThird Party AdvisoryVDB Entry
- www.seekurity.com/blog/general/metasploit-web-project-kill-all-running-tasks-csrf-CVE-2017-5244/nvdThird Party Advisory
News mentions
0No linked articles in our index yet.