[Security] Bump schema-inspector from 1.6.8 to 2.0.0

[dependabot-preview]

Bumps schema-inspector from 1.6.8 to 2.0.0. This update includes security fixes.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Regular Expression Denial-of-Service in npm schema-inspector

Impact

What kind of vulnerability is it? Who is impacted? Email address validation is vulnerable to a denial-of-service attack where some input (for example a@0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.) will freeze the program or web browser page executing the code. This affects any current schema-inspector users using any version to validate email addresses. Users who do not do email validation, and instead do other types of validation (like string min or max length, etc), are not affected.

Patches

Has the problem been patched? What versions should users upgrade to? Users should upgrade to version 2.0.0, which uses a regex expression that isn't vulnerable to ReDoS. The new regex expression is more limited in what it can check, so it is more flexible than the one used before. Therefore, this was a new major version instead of a new patch version to warn people upgrading that they should make sure the email validation still works for their use case.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading? If a user chooses to not upgrade, the only known workaround would be to stop using the email validation feature in the library. The user could, for example, accept the email address into their system but save it in a "not yet validated" state in their system until a verification email is sent to it (to determine whether the email is valid and belongs to the form submitter). Note that this is the preferred way of validating email addresses anyways.

References

Are there any links users can visit to find out more? https://gist.github.com/mattwelke/b7f42424680a57b8161794ad1737cd8f

For more information

If you have any questions or comments about this advisory, you can create an issue in this repository.

Affected versions: < 2.0.0

Sourced from The GitHub Security Advisory Database.

Validation Bypass in schema-inspector In schema-inspector before 1.6.9, a maliciously crafted JavaScript object can bypass the sanitize() and the validate() function used within schema-inspector.

Affected versions: < 1.6.9

Release notes

Sourced from schema-inspector's releases.

v2.0.0

To fix a security vulnerability (CVE-2021-21267) in the 1.x.x email Regex expression used, a new Regex expression was used which may be less flexible than the expression used in 1.x.x. Therefore, version 2.0.0 was released with this new expression. It's highly-recommended to upgrade to this new version after testing it.

If you need the old, insecure behavior, use version 1.x.x or use the custom validation function feature for your field and perform email address validation any way you like.

v1.7.0

• Adds support for v4 UUID strings (ex. a4c46b74-cf00-4cd0-9100-e121ce4b67de) using regex. See README for usage example. See Atinux/schema-inspector#79 (PR by @ViniciusFXavier )

v1.6.10

• fix #77: change version of async dep to ~2.6.3 for IE compatibility (PR #80 by @mattwelke)

v1.6.9

• Upgrade dependencies
• Fix Atinux/schema-inspector#75 and Atinux/schema-inspector#76

Commits

• e02ea1f update readme regarding 2.0.0
• 49fa4b7 Fix email regex security vulnerability (GHSL-2020-358) by replacing regex (#92)
• 8e0610d Merge pull request #89 from schema-inspector/dependabot/npm_and_yarn/mocha-8.3.0
• 005a9b3 Bump mocha from 7.0.0 to 8.3.0
• e88803b Merge pull request #87 from ViniciusFXavier/patch-1
• 26df7bb Update README.md
• ca5a7a9 Create dependabot.yml
• 8b8fea0 Create codeql-analysis.yml (#84)
• d4e782c Replace link to vendored jquery file in frontEndTest.html with latest… (#81)
• a6b8de4 1.7.0
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by mattwelke, a new releaser for schema-inspector since your current version.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)