[Security] Bump axios from 0.19.2 to 0.21.1

[dependabot-preview]

Bumps axios from 0.19.2 to 0.21.1. This update includes a security fix.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Server-Side Request Forgery in Axios Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.

Affected versions: < 0.21.1

Release notes

Sourced from axios's releases.

v0.21.1

0.21.1 (December 21, 2020)

Fixes and Functionality:

• Hotfix: Prevent SSRF (#3410)
• Protocol not parsed when setting proxy config from env vars (#3070)
• Updating axios in types to be lower case (#2797)
• Adding a type guard for AxiosError (#2949)

Internal and Tests:

• Remove the skipping of the socket http test (#3364)
• Use different socket for Win32 test (#3375)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

• Daniel Lopretto [email protected]
• Jason Kwok [email protected]
• Jay [email protected]
• Jonathan Foster [email protected]
• Remco Haszing [email protected]
• Xianming Zhong [email protected]

v0.21.0

0.21.0 (October 23, 2020)

Fixes and Functionality:

• Fixing requestHeaders.Authorization (#3287)
• Fixing node types (#3237)
• Fixing axios.delete ignores config.data (#3282)
• Revert "Fixing overwrite Blob/File type as Content-Type in browser. (#1773)" (#3289)
• Fixing an issue that type 'null' and 'undefined' is not assignable to validateStatus when typescript strict option is enabled (#3200)

Internal and Tests:

• Lock travis to not use node v15 (#3361)

Documentation:

• Fixing simple typo, existant -> existent (#3252)
• Fixing typos (#3309)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

• Allan Cruz [email protected]
• George Cheng [email protected]
• Jay [email protected]
• Kevin Kirsche [email protected]

Changelog

Sourced from axios's changelog.

0.21.1 (December 21, 2020)

Fixes and Functionality:

• Hotfix: Prevent SSRF (#3410)
• Protocol not parsed when setting proxy config from env vars (#3070)
• Updating axios in types to be lower case (#2797)
• Adding a type guard for AxiosError (#2949)

Internal and Tests:

• Remove the skipping of the socket http test (#3364)
• Use different socket for Win32 test (#3375)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

• Daniel Lopretto [email protected]
• Jason Kwok [email protected]
• Jay [email protected]
• Jonathan Foster [email protected]
• Remco Haszing [email protected]
• Xianming Zhong [email protected]

0.21.0 (October 23, 2020)

Fixes and Functionality:

• Fixing requestHeaders.Authorization (#3287)
• Fixing node types (#3237)
• Fixing axios.delete ignores config.data (#3282)
• Revert "Fixing overwrite Blob/File type as Content-Type in browser. (#1773)" (#3289)
• Fixing an issue that type 'null' and 'undefined' is not assignable to validateStatus when typescript strict option is enabled (#3200)

Internal and Tests:

• Lock travis to not use node v15 (#3361)

Documentation:

• Fixing simple typo, existant -> existent (#3252)
• Fixing typos (#3309)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

• Allan Cruz [email protected]
• George Cheng [email protected]
• Jay [email protected]
• Kevin Kirsche [email protected]
• Remco Haszing [email protected]
• Taemin Shin [email protected]

Commits

• a64050a Releasing 0.21.1
• d57cd97 Updating changelog for 0.21.1 release
• 8b0f373 Use different socket for Win32 test (#3375)
• e426910 Protocol not parsed when setting proxy config from env vars (#3070)
• c7329fe Hotfix: Prevent SSRF (#3410)
• f472e5d Adding a type guard for AxiosError (#2949)
• 7688255 Remove the skipping of the socket http test (#3364)
• 820fe6e Updating axios in types to be lower case (#2797)
• 94ca24b Releasing 0.21.0
• 2130a0c Updating changelog for 0.21.0 release
• 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 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)

[merge-mamba]

Potential Conflict Warning

This pull request has changes that overlap with branches below. You might want to check in with the other
branch authors before you merge to avoid a conflict. 🐍

dependabot/npm_and_yarn/bl-2.2.1 (@dependabot-preview[bot])

• package-lock.json (modified)

dependabot/npm_and_yarn/mongodb-4.0.0 (@dependabot-preview[bot])

• package.json (modified)
• package-lock.json (modified)

dependabot/npm_and_yarn/node-fetch-2.6.1 (@dependabot[bot])

• package-lock.json (modified)

dependabot/npm_and_yarn/elliptic-6.5.4 (@dependabot-preview[bot])

• package-lock.json (modified)

dependabot/npm_and_yarn/lodash-4.17.21 (@dependabot-preview[bot])

• package-lock.json (modified)

dependabot/npm_and_yarn/vue-router-3.5.2 (@dependabot-preview[bot])

• package-lock.json (modified)
• package.json (modified)

dependabot/npm_and_yarn/browserslist-4.16.6 (@dependabot[bot])

• package-lock.json (modified)

dependabot/npm_and_yarn/axios-0.21.1 (@dependabot-preview[bot])

• package.json (modified)
• package-lock.json (modified)

dependabot/npm_and_yarn/vue/cli-plugin-eslint-4.5.13 (@dependabot-preview[bot])

• package-lock.json (modified)
• package.json (modified)

dependabot/npm_and_yarn/dns-packet-1.3.4 (@dependabot[bot])

• package-lock.json (modified)

dependabot/npm_and_yarn/vue/cli-plugin-babel-4.5.13 (@dependabot-preview[bot])

• package.json (modified)
• package-lock.json (modified)

dependabot/npm_and_yarn/bootstrap-vue-2.21.2 (@dependabot-preview[bot])

• package-lock.json (modified)
• package.json (modified)

dependabot/npm_and_yarn/y18n-3.2.2 (@dependabot-preview[bot])

• package-lock.json (modified)

dependabot/npm_and_yarn/postcss-7.0.36 (@dependabot[bot])

• package-lock.json (modified)

Something wrong? Got a suggestion? Email me or leave feedback here.

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.