[Security] Bump tough-cookie from 2.3.2 to 2.3.4

[dependabot-preview]

Bumps tough-cookie from 2.3.2 to 2.3.4. This update includes security fixes.

Vulnerabilities fixed

Sourced from The npm Advisory Database.

Regular Expression Denial of Service
Affected versions of tough-cookie are susceptible to a regular expression denial of service.

The amplification on this vulnerability is relatively low - it takes around 2 seconds for the engine to execute on a malicious input which is 50,000 characters in length.

If node was compiled using the -DHTTP_MAX_HEADER_SIZE however, the impact of the vulnerability can be significant, as the primary limitation for the vulnerability is the default max HTTP header length in node.

Affected versions: <2.3.3

Sourced from The GitHub Security Advisory Database.

High severity vulnerability that affects tough-cookie
A ReDoS (regular expression denial of service) flaw was found in the tough-cookie module before 2.3.3 for Node.js. An attacker that is able to make an HTTP request using a specially crafted cookie may cause the application to consume an excessive amount of CPU.

Affected versions: < 2.3.3

Sourced from The GitHub Security Advisory Database.

High severity vulnerability that affects tough-cookie
A ReDoS (regular expression denial of service) flaw was found in the tough-cookie module before 2.3.3 for Node.js. An attacker that is able to make an HTTP request using a specially crafted cookie may cause the application to consume an excessive amount of CPU.

Affected versions: <2.3.3

Commits

• e4dfb0a 2.3.4
• 7d66ffd Update public suffix list
• 7564c06 Merge pull request #100 from salesforce/no-re-parser
• 751da6d Document removal of 256 space limit
• 8452ccd Convert date-time parser from regexp, expand tests
• 8614dbf More String#repeat polyfill
• 2a4775c Avoid unbounded Regexp parts in date parsing
• c9bd79d Parse cookie-pair part without regexp
• 12d4266 2.3.3
• 98e0916 Merge pull request #97 from salesforce/spaces-ReDoS
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 cancel merge will cancel a previously requested merge
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• 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)

Finally, you can contact us by mentioning @dependabot.