CVE-2019-20174: XSS

Published Jan 31, 2020
·
Updated

Overview

Auth0 Lock version 11.20.4 and earlier did not properly sanitize the generated HTML code. Customers using the additionalSignUpFields customization option to add a checkbox to the sign-up dialog that are passing a placeholder property obtained from an untrusted source (e.g. a query parameter) could allow cross-site scripting (XSS) on their signup pages.

Am I affected?

You are affected by this vulnerability if all of the following conditions apply:

- You are using Auth0 Lock version 11.20.4 or earlier. - You pass additionalSignUpFields as options when initializing Lock which includes a field of type checkbox whose placeholder value is obtained from an untrusted source.

An example of a vulnerable snippet is the following where the placeholder value is partially user-controlled by the name query parameter:

javascript <script> var params = new URLSearchParams(window.location.search); var options = { auth: { redirectUrl: 'http://localhost:12345/callback', responseType: 'code', params: { scope: 'openid email', }, }, additionalSignUpFields: [{ name: 'agree', type: 'checkbox', placeholder: "I agree to Terms and Conditions for " + params.get('name'), }], }; var lock = new Auth0Lock('<CLIENTID>', '<TENANTNAME>.auth0.com', options); lock.show({ allowShowPassword: true, initialScreen: 'signUp', }); </script>

How to fix that?

Developers using Auth0’s signin solution Lock need to upgrade to version 11.21.0 or later. Version 11.21.0 introduces two changes:

1. The existing placeholder property is now treated as plain text to mitigate the problem. 2. A new placeholderHTML property is introduced that indicates the level of control it provides and that it should be only supplied from trusted sources.

Will this update impact my users?

This fix patches the Auth0 Lock widget and may require changes in application code, but it will not impact your users, their current state, or any existing sessions.

Developers using the placeholder property with HTML content from a trusted source should start using the placeholderHTML property to continue providing the same user experience.

Other sources

Auth0 Lock before 11.21.0 allows XSS when additionalSignUpFields is used with an untrusted placeholder.

Affected Software

2 affected componentsFixes available
npm/auth0-lock<11.21.0
11.21.0
Auth0 Lock<11.21.0

Event History

Jan 31, 2020
Advisory Published
05:59 PM
Feb 3, 2020
CVE Published
via MITRE·05:13 PM
Data Sourced
via MITRE·05:13 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2019-20174?

CVE-2019-20174 has a medium severity rating due to potential security risks related to improper HTML sanitization.

2

How do I fix CVE-2019-20174?

To fix CVE-2019-20174, upgrade Auth0 Lock to version 11.21.0 or later where the vulnerability is resolved.

3

What versions of Auth0 Lock are affected by CVE-2019-20174?

Auth0 Lock versions 11.20.4 and earlier are affected by CVE-2019-20174.

4

What is the nature of the vulnerability in CVE-2019-20174?

CVE-2019-20174 is a vulnerability that arises from the lack of proper sanitization of generated HTML code.

5

What customization option increases the risk in CVE-2019-20174?

The risk in CVE-2019-20174 is increased when using the 'additionalSignUpFields' customization option with untrusted sources.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203