First published: Thu May 05 2022(Updated: )
Auth0 is an authentication broker that supports both social and enterprise identity providers, including Active Directory, LDAP, Google Apps, and Salesforce. In versions before `11.33.0`, when the “additional signup fields” feature [is configured](https://github.com/auth0/lock#additional-sign-up-fields), a malicious actor can inject invalidated HTML code into these additional fields, which is then stored in the service `user_metdata` payload (using the `name` property). Verification emails, when applicable, are generated using this metadata. It is therefor possible for an actor to craft a malicious link by injecting HTML, which is then rendered as the recipient's name within the delivered email template. You are impacted by this vulnerability if you are using `auth0-lock` version `11.32.2` or lower and are using the “additional signup fields” feature in your application. Upgrade to version `11.33.0`.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Auth0 Lock | <11.33.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-29172 is classified as a medium severity vulnerability affecting Auth0 Lock prior to version 11.33.0.
To fix CVE-2022-29172, upgrade Auth0 Lock to version 11.33.0 or higher.
CVE-2022-29172 affects Auth0 Lock versions before 11.33.0 used in Node.js environments.
CVE-2022-29172 pertains to security risks associated with the 'additional signup fields' feature in Auth0 Lock.
Yes, CVE-2022-29172 is a publicly disclosed vulnerability with specific versions impacted.