Vulnerability in logto-io logto

[ Description ]Official 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.

[ Fixes ]Fixes and patches

No fix or interim patch is linked from our sources yet. Check the vendor references below and limit exposure of affected systems until a fix is available.

[ References ]References

• github.com/logto-io/logto/commit/16f4b2e732d5114ac98646c9370ec6ab61d6ed26
• github.com/logto-io/logto/pull/9501
• github.com/logto-io/logto/releases/tag/v1.43.0
• github.com/logto-io/logto/security/advisories/GHSA-3556-624q-c5w3