CVE-2022-29172: Auth0 lock Cross-Site Scripting Vulnerability

MODERATE
Advisory Identifier: GHSA-7ww6-75fj-jcj7
CVSS 6.1
CWE-79
Published
Advisory Summary

CVE-2022-29172 is a MODERATE (CVSS 6.1) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Auth0 lock libraries in the npm ecosystem. The issue involves cross-site scripting in auth0 lock. Remediation is available by upgrading affected packages to version 11.33.0.

CVE-2022-29172 at a Glance

CVE Identifier CVE-2022-29172
GHSA Identifier GHSA-7ww6-75fj-jcj7
Severity MODERATE
CVSS v3.1 Base Score 6.1
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Auth0 lock
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 6.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2022-29172

To remediate this vulnerability, upgrade all affected Auth0 lock dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

auth0-lock fixed: 11.33.0
npm install auth0-lock@11.33.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls auth0-lock

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2022-29172, inspect your project dependencies using npm:

npm ls auth0-lock

Analyze the terminal output to locate any version of Auth0 lock in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 11.33.0), your application is affected.

Note: The npm ls auth0-lock command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Auth0 lock, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Overview In versions before and including `11.32.2`, 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. ### Am I affected? 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. ### How to fix that? Upgrade to version `11.33.0`. ### Will this update impact my users? Additional signup fields that have been added to the signup tab on Lock will have HTML tags stripped from user input from version `11.33.0` onwards. The user will not receive any validation warning or feedback, but backend data will no longer include HTML.

CVE-2022-29172 Affected Auth0 lock Versions

1 component(s)
Fixed Versions:
11.33.0
Product / Package Ecosystem Affected Versions Fixed Version
auth0-lock
npm
< 11.33.0
11.33.0

References

Frequently Asked Questions

What is CVE-2022-29172?
CVE-2022-29172 is a security vulnerability in Auth0 lock involving Cross-site Scripting in Auth0 Lock under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Auth0 lock versions are affected?
Affected versions include releases prior to 11.33.0 across affected packages: auth0-lock.
What version fixes CVE-2022-29172?
Upgrading to 11.33.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is auth0-lock affected?
Yes, auth0-lock is affected in releases prior to 11.33.0. Upgrade your dependency to 11.33.0 or later.
What is the CVSS score of CVE-2022-29172?
CVE-2022-29172 has a CVSS v3.1 base score of 6.1 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N.
What CWE is associated with CVE-2022-29172?
CVE-2022-29172 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check npm dependencies for CVE-2022-29172?
Run the dependency tree command: 'npm ls auth0-lock'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7ww6-75fj-jcj7",
  "modified" : "2022-05-24T20:49:20Z",
  "published" : "2022-05-24T20:49:20Z",
  "aliases" : [ "CVE-2022-29172" ],
  "summary" : "Cross-site Scripting in Auth0 Lock",
  "details" : "### Overview\n\nIn versions before and including `11.32.2`, 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).\n\nVerification 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.\n\n### Am I affected?\nYou 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.\n\n### How to fix that?\nUpgrade to version `11.33.0`.\n\n### Will this update impact my users?\nAdditional signup fields that have been added to the signup tab on Lock will have HTML tags stripped from user input from version `11.33.0` onwards. The user will not receive any validation warning or feedback, but backend data will no longer include HTML.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "auth0-lock"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "11.33.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/auth0/lock/security/advisories/GHSA-7ww6-75fj-jcj7"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-29172"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/auth0/lock/commit/79ae557d331274b114848150f19832ae341771b1"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/auth0/lock"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-05-24T20:49:20Z",
    "nvd_published_at" : "2022-05-05T23:15:00Z"
  }
}