جزئیات آسیب‌پذیری

Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's Account Center step-up check accepted any active verification record that belonged to the current user and had isVerified === true. A WebAuthn registration verification record for binding a new passkey could be created and verified with only an existing Account API bearer token, then sent in the logto-verification-id header and treated as identityVerified=true by Account Center routes, allowing MFA factor management without proving possession of an existing password, identifier, or MFA factor. This issue is fixed in version 1.41.0.

• https://github.com/logto-io/logto/pull/9110 x_refsource_MISC
• https://github.com/logto-io/logto/commit/f56255a7edf3b22b0ec2fdb814814ce6b0123b74 x_refsource_MISC
• https://github.com/logto-io/logto/releases/tag/v1.41.0 x_refsource_MISC
• https://github.com/logto-io/logto/security/advisories/GHSA-q4h3-38gc-4p4j x_refsource_CONFIRM