Medplum
Medplum - Improper Validation of Redirect URI in External Auth Callback allows Authorization Code Leakage
Medplum is a developer platform that enables development of healthcare apps. Prior to version 5.1.6, the external identity provider callback at GET /auth/external accepts attacker-controlled redirect URIs that only need to start with a registered client redirect URI, rather than matching exactly. After a successful external IdP login, the server appends Medplum login and code values to that attacker-supplied URL and issues a redirect. Because the external login request state is serialized as raw JSON and later trusted by the callback, an attacker who can tamper with state.redirectUri can cause Medplum to redirect authorization artifacts to an attacker-controlled endpoint. When the registered redirect URI is a bare origin or another prefix that can be extended into a different hostname, this becomes a cross-origin authorization code leak. This issue has been patched in version 5.1.6.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 5.1.6
Fixed in 5.1.6
Mitigation
Upgrade medplum to 5.1.6 or later.
References
- Vendor advisory github.com/medplum/medplum/security/advisories…
- Patch github.com/medplum/medplum/pull/8749
- Patch github.com/medplum/medplum/commit/7ae10035ddad…
1 more
- Release notes github.com/medplum/medplum/releases/tag/v5.1.6
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.