The Metasploit Framework Web Service REST API (msf-ws) exposes the credential store through…

Why it is Amber

• CVSS 9.8 critical
• Remotely exploitable without logging in

References

• https://github.com/rapid7/metasploit-framework
• https://github.com/rapid7/metasploit-framework/releases/tag/6.5.5
• https://github.com/rapid7/metasploit-framework/releases/tag/6.5.5
• https://github.com/rapid7/metasploit-framework/releases/tag/6.5.5
• https://github.com/rapid7/metasploit-framework/releases/tag/6.5.5
• https://github.com/rapid7/metasploit-framework/releases/tag/6.5.5
• https://github.com/rapid7/metasploit-framework/releases/tag/6.5.5
• https://github.com/rapid7/metasploit-framework/releases/tag/6.5.5
• https://github.com/rapid7/metasploit-framework/releases/tag/6.5.5

Original description

The Metasploit Framework Web Service REST API (msf-ws) exposes the credential store through Msf::WebServices::CredentialServlet. Every mutating and read route in this servlet calls warden.authenticate! before processing a request, except the update_credential (PUT) and delete_credentials (DELETE) handlers for /api/v1/credentials, which omit the authentication call entirely. Because these handlers call directly into lib/msf/core/db_manager/cred.rb, which performs no authorization check of its own, any client able to reach the web service on its default 0.0.0.0:8080 listener can read, modify, or permanently delete every stored credential record — including passwords, hashes, and private keys stored for a shared team engagement — without presenting any authentication. All published versions of Metasploit Framework through 6.5.4 are affected. The issue is fixed in 6.5.5 by adding warden.authenticate! as the first statement in both handlers, matching the pattern used by every other route in the API.