Logto: SSRF via Webhooks and Custom OAuth2 Connector UserInfo Endpoint
What fixes it
- 1.43.0@logto/core, npmGitHub
npm install @logto/core@1.43.0
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.43.0, Logto fetches administrator-controlled outbound destinations without validating the address used for the connection. Webhook delivery in packages/core/src/libraries/hook/utils.ts can reach special-use and cloud metadata addresses. Custom OAuth2 connectors can use an attacker-selected userInfoEndpoint and forward the OAuth access token in the Authorization header, while OIDC connectors can fetch an attacker-selected jwksUri. The affected operations require tenant administrative configuration access, but they cross the server's network boundary and can expose internal data or upstream provider credentials. This issue is fixed in version 1.43.0.
Text from CVE List
Affected versions 2
- logtoaffected: < 1.43.0CVE List
- @logto/core, npm<= 1.42.0GitHub