{"answers":{"affected":"2 open source packages ship an affected version, including auth0-lock. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29172 in the wild and no public exploit code.","fix":"Upgrade auth0-lock to 11.33.0 or later.","what":"CVE-2022-29172 is a medium-severity cross-site scripting vulnerability in auth0 lock, published on 5 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-29172 and fix it if it is affected.\n\nWhat it is: CVE-2022-29172 is a medium-severity cross-site scripting vulnerability in auth0 lock, published on 5 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-29172 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- auth0-lock (npm): affected all versions; fixed in 11.33.0\n- auth0-lock (npm): affected all versions; fixed in 11.33.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-29172/ (Markdown: https://insights.sbomify.com/CVE-2022-29172/index.md)","id":"CVE-2022-29172","markdown":"https://insights.sbomify.com/CVE-2022-29172/index.md","name":"CVE-2022-29172","record":{"aliases":["GHSA-7ww6-75fj-jcj7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Auth0 Lock library","requires_auth":"none","summary":"Attackers can inject HTML into signup fields to execute scripts in verification emails, affecting Auth0 Lock users with additional signup fields enabled.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"lock","vendor":"auth0"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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`.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"HTML injection with additional signup fields","id":"CVE-2022-29172","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"No protection against rollback attacks in go-tuf","id":"CVE-2022-29173"},"packages":[{"ecosystem":"npm","fixed":["11.33.0"],"introduced":["0"],"last_affected":[],"package":"auth0-lock","purl":null,"source":"GHSA-7ww6-75fj-jcj7"},{"ecosystem":"npm","fixed":["11.33.0"],"introduced":["0"],"last_affected":[],"package":"auth0-lock","purl":"pkg:npm/auth0-lock","source":"GHSA-7ww6-75fj-jcj7"}],"prev":{"headline":"Remote Code Execution in sourcegraph","id":"CVE-2022-29171"},"products":["lock"],"published":"2022-05-05","related":[{"cvss_score":8.1,"headline":"Reflected XSS when using flashMessages","id":"CVE-2021-32641","kev_date_added":null,"published":"2021-06-04"},{"cvss_score":6.4,"headline":"DOM-based XSS in auth0-lock","id":"CVE-2020-15119","kev_date_added":null,"published":"2020-08-19"},{"cvss_score":6.1,"headline":"auth0-lock vulnerable to XSS via unsanitized placeholder property","id":"CVE-2019-20174","kev_date_added":null,"published":"2020-02-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["auth0"]},"summary":"Attackers can inject HTML into signup fields to execute scripts in verification emails, affecting Auth0 Lock users with additional signup fields enabled.","url":"https://insights.sbomify.com/CVE-2022-29172/"}