Bump form-data and passport-auth0 in /app3.com#18
Conversation
Bumps [form-data](https://github.com/form-data/form-data) to 4.0.6 and updates ancestor dependency [passport-auth0](https://github.com/auth0/passport-auth0). These dependencies need to be updated together. Updates `form-data` from 2.3.1 to 4.0.6 - [Changelog](https://github.com/form-data/form-data/blob/master/CHANGELOG.md) - [Commits](form-data/form-data@v2.3.1...v4.0.6) Updates `passport-auth0` from 0.5.2 to 1.4.5 - [Release notes](https://github.com/auth0/passport-auth0/releases) - [Changelog](https://github.com/auth0/passport-auth0/blob/master/CHANGELOG.md) - [Commits](auth0/passport-auth0@v0.5.2...v1.4.5) --- updated-dependencies: - dependency-name: form-data dependency-version: 4.0.6 dependency-type: indirect - dependency-name: passport-auth0 dependency-version: 1.4.5 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![semgrep-code-auth0-samples[bot]](https://avatars.githubusercontent.com/in/1042765?s=60&v=4){kind=small}
| } | ||
| }, | ||
| "jsonwebtoken": { | ||
| "node_modules/jsonwebtoken": { |
There was a problem hiding this comment.
Medium severity vulnerability may affect your project—review required:
Line 737 lists a dependency (jsonwebtoken) with a known Medium severity vulnerability.
ℹ️ Why this matters
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.
To resolve this comment:
Check if you are using a poorly implemented key retrieval function and your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function..
- If you're affected, upgrade this dependency to at least version 9.0.0 at app3.com/package-lock.json.
- If you're not affected, comment
/fp we don't use this [condition]
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
| } | ||
| }, | ||
| "jsonwebtoken": { | ||
| "node_modules/jsonwebtoken": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 737 lists a dependency (jsonwebtoken) with a known High severity vulnerability.
ℹ️ Why this matters
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.
To resolve this comment:
Check if you are using a legacy, insecure key type with a supported algorithm; for example, DSA keys could be used with the RS256 algorithm.
- If you're affected, upgrade this dependency to at least version 9.0.0 at app3.com/package-lock.json.
- If you're not affected, comment
/fp we don't use this [condition]
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
| } | ||
| }, | ||
| "swig": { | ||
| "node_modules/swig": { |
There was a problem hiding this comment.
High severity vulnerability introduced by a package you're using:
Line 1144 lists a dependency (swig) with a known High severity vulnerability. Fixing requires upgrading or replacing the dependency.
ℹ️ Why this matters
swig versions before and including 1.4.2 and swig-templates versions before and including 2.0.4 are vulnerable to Improper Limitation Of A Pathname To A Restricted Directory ('Path Traversal'). An attacker can read arbitrary files via the include or extends tags, during template rendering. This repository has been archived by the owner and is no longer maintained.
To resolve this comment:
Upgrade this dependency as soon as a patched version is available.
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
Bumps form-data to 4.0.6 and updates ancestor dependency passport-auth0. These dependencies need to be updated together.
Updates
form-datafrom 2.3.1 to 4.0.6Changelog
Sourced from form-data's changelog.
... (truncated)
Commits
64190dbv4.0.692ae0eb[Deps] updatehasown,mime-typesf31d21e[Dev Deps] update@ljharb/eslint-config,auto-changelog,tape8dff42c[Fix] escape CR, LF, and"in field names and filenames67b0f65[Dev Deps] updatejs-randomness-predictor68ff7ddv4.0.55822467[Dev Deps] update@ljharb/eslint-config,eslint76d0dee[Fix] set Symbol.toStringTag in the proper place16e0076[Tests] Switch to newer v8 prediction library; enable node 24 testing41996f5v4.0.4Maintainer changes
This version was pushed to npm by ljharb, a new releaser for form-data since your current version.
Install script changes
This version modifies
prepublishscript that runs during installation. Review the package contents before updating.Updates
passport-auth0from 0.5.2 to 1.4.5Release notes
Sourced from passport-auth0's releases.
... (truncated)
Changelog
Sourced from passport-auth0's changelog.
... (truncated)
Commits
0f2ee56Release v1.4.5 (#216)d48e01eRelease v1.4.54445b81chore(ci): Remove Semgrep GHA Workflow (#205)65343e9chore:removing semgrep static workflow and back-merging with master20cee6fBump actions/setup-node from 4 to 6 (#214)f913d70Merge branch 'master' into dependabot/github_actions/actions/setup-node-64db0a73Bump github/codeql-action from 3 to 4 (#213)595e8f5Merge branch 'master' into dependabot/github_actions/github/codeql-action-4264d381Bump codecov/codecov-action from 3.1.6 to 5.5.1 (#212)741954fMerge branch 'master' into dependabot/github_actions/codecov/codecov-action-5...Maintainer changes
This version was pushed to npm by auth0-oss, a new releaser for passport-auth0 since your current version.
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 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.