Vulnerabilities · 2017 · Rapid7
CVE-2017-5244
Rapid7 Metasploit vulnerability
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.
Affected products
Metasploit. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Rapid7 Metasploit runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- community.rapid7.com/community/metasploit/blog/2017/06/15/r7-2017-16-cve-2017-5244-lack-of · Exploit
- www.securityfocus.com/bid/99082 · Third Party Advisory
- www.seekurity.com/blog/general/metasploit-web-project-kill-all-running-tasks-csrf-CVE-2017 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2017-5244
- cve.org/CVERecord?id=CVE-2017-5244
More vulnerabilities in Rapid7 products
CVE-2025-36857CVE-2025-11195CVE-2025-6264CVE-2025-4951CVE-2024-8042CVE-2024-6504CVE-2024-2745CVE-2023-5950All 74
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.