Modelcontextprotocol rust-sdk
RMCP: Missing Resource Field Validation in OAuth Protected Resource Metadata Discovery
RMCP is an official Rust SDK for the Model Context Protocol. Prior to 2.0.0, the rmcp crate's OAuth implementation in crates/rmcp/src/transport/auth.rs omits the RFC 9728 resource field from ResourceServerMetadata and allows discover_oauth_server_via_resource_metadata to use protected-resource metadata without confirming that the returned resource identifier exactly matches the configured MCP server. A malicious MCP server can publish metadata for a different legitimate MCP resource and its authorization server, causing a victim who connects and completes the authorization flow to obtain a legitimate access token that the client subsequently sends to the malicious server. The attacker can capture the token and impersonate the victim against the legitimate MCP resource within the token's granted scopes. This issue is fixed in version 2.0.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.0.0
Fixed in 2.0.0
Mitigation
Upgrade rust-sdk to 2.0.0 or later.
References
- Vendor advisory github.com/modelcontextprotocol/rust-sdk/secur…
- Patch github.com/modelcontextprotocol/rust-sdk/pull/…
- Patch github.com/modelcontextprotocol/rust-sdk/commi…
1 more
- Release notes github.com/modelcontextprotocol/rust-sdk/relea…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.