build(deps): bump axios from 0.21.4 to 0.30.0 #217
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [axios](https://github.com/axios/axios) from 0.21.4 to 0.30.0. - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v0.30.0/CHANGELOG.md) - [Commits](axios/axios@v0.21.4...v0.30.0) --- updated-dependencies: - dependency-name: axios dependency-version: 0.30.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
![prisma-cloud-devsecops[bot]](https://avatars.githubusercontent.com/in/135857?s=60&v=4){kind=small}
| "@sectester/runner": "^0.16.5", | ||
| "@sectester/scan": "^0.16.5", | ||
| "axios": "^0.21.4", | ||
| "axios": "^0.30.0", |
There was a problem hiding this comment.
axios 0.30.0 / package.json
Total vulnerabilities: 1
| Critical: 0 | High: 0 | Medium: 1 | Low: 0 |
|---|
| Vulnerability ID | Severity | CVSS | Fixed in | Status |
|---|---|---|---|---|
| CVE-2024-28849 |  MEDIUM |
6.5 | - |
Open |
|
Semgrep found 1 Risk: Affected versions of jsonwebtoken are vulnerable to Improper Authentication. Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC. Manual Review Advice: A vulnerability from this advisory is reachable if you are using a poorly implemented key retrieval function and your application is supporting usage of both symmetric key and asymmetric key in Fix: Upgrade this library to at least version 9.0.0 at brokencrystals/package-lock.json:10311. Reference(s): GHSA-hjrf-2m68-5959, CVE-2022-23541 Semgrep found 1 Risk: Affected versions of jsonwebtoken are vulnerable to Use Of A Broken Or Risky Cryptographic Algorithm. The library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm. Manual Review Advice: A vulnerability from this advisory is reachable if you are using a legacy, insecure key type with a supported algorithm; for example, DSA keys could be used with the RS256 algorithm Fix: Upgrade this library to at least version 9.0.0 at brokencrystals/package-lock.json:10311. Reference(s): GHSA-8cf7-32gw-wr33, CVE-2022-23539 Semgrep found 1 Risk: webpack 5.x before 5.76.0 is vulnerable to Improper Access Control due to ImportParserPlugin.js mishandling the magic comment feature. Due to this, webpack does not avoid cross-realm object access and an attacker who controls a property of an untrusted object can obtain access to the real global object. Manual Review Advice: A vulnerability from this advisory is reachable if you host an application utilizing webpack and an attacker can control a property of an untrusted object Fix: Upgrade this library to at least version 5.76.0 at brokencrystals/package-lock.json:15827. Reference(s): GHSA-hc6q-2mpp-qw7j, CVE-2023-28154 |
|
Semgrep found 1 Risk: Affected versions of jsonwebtoken are vulnerable to Improper Authentication. Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC. Manual Review Advice: A vulnerability from this advisory is reachable if you are using a poorly implemented key retrieval function and your application is supporting usage of both symmetric key and asymmetric key in Fix: Upgrade this library to at least version 9.0.0 at brokencrystals/package-lock.json:10311. Reference(s): GHSA-hjrf-2m68-5959, CVE-2022-23541 Semgrep found 1 Risk: Affected versions of jsonwebtoken are vulnerable to Use Of A Broken Or Risky Cryptographic Algorithm. The library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm. Manual Review Advice: A vulnerability from this advisory is reachable if you are using a legacy, insecure key type with a supported algorithm; for example, DSA keys could be used with the RS256 algorithm Fix: Upgrade this library to at least version 9.0.0 at brokencrystals/package-lock.json:10311. Reference(s): GHSA-8cf7-32gw-wr33, CVE-2022-23539 Semgrep found 1 Risk: webpack 5.x before 5.76.0 is vulnerable to Improper Access Control due to ImportParserPlugin.js mishandling the magic comment feature. Due to this, webpack does not avoid cross-realm object access and an attacker who controls a property of an untrusted object can obtain access to the real global object. Manual Review Advice: A vulnerability from this advisory is reachable if you host an application utilizing webpack and an attacker can control a property of an untrusted object Fix: Upgrade this library to at least version 5.76.0 at brokencrystals/package-lock.json:15827. Reference(s): GHSA-hc6q-2mpp-qw7j, CVE-2023-28154 |
|
New Issues (124)Checkmarx found the following issues in this Pull Request
Fixed Issues (4)Great job! The following issues were fixed in this Pull Request
|
|
Superseded by #231. |
Bumps axios from 0.21.4 to 0.30.0.
Release notes
Sourced from axios's releases.
... (truncated)
Changelog
Sourced from axios's changelog.
... (truncated)
Commits
6e922e4chore: added build artifactsa06ed1echore: added pre-release artifactsc010622feat: add type for allowAbsoluteUrls (#6849)02c3c69fix: backport allowAbsoluteUrls vuln fix to v0.x (#6829)8603e67docs: modify upgrade guide for 0.28.1's breaking change (#6787)f0642eefix(docs): update CHANGELOG.md for v0.x (#6271)0630c32fix: modify log while request is aborted (#4917)7750b8cchore(release): prep release v0.29.04840cb2fix: regular expression denial of service issues (#6708)2e36cdbfix(backport): fix paramsSerializer function validation (#6361)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.