Skip to content

[Snyk] Security upgrade aegir from 14.0.0 to 20.0.0 #180

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: CircleCI-v2
Choose a base branch
from

Conversation

snyk-bot
Copy link

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • examples/circuit-relaying/package.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
critical severity 791/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 9.4
Server-side Request Forgery (SSRF)
SNYK-JS-PARSEURL-2936249
Yes Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: aegir The new version differs by 176 commits.
  • 33f716a chore: release version v20.0.0
  • 1e0bb42 chore: update contributors
  • ca63d17 fix: use the default docs theme (#396)
  • 7db9e4c feat: update deps and make lint --fix work (#395)
  • 690c459 feat: aegir test --100 for full coverage validation (#360)
  • 988d40a chore: release version v19.0.5
  • afe222f chore: update contributors
  • 717f888 feat: support async hooks (#390)
  • 1026032 chore: release version v19.0.4
  • 4ff0095 chore: update contributors
  • 4ad7f19 fix: use default babel config and update browserslist (#382)
  • 63d33e1 Merge branch 'master' of github.com:ipfs/aegir
  • ff6e16b fix: update docs for electron ci config
  • e098b1d chore(deps): update @ commitlint/config-conventional requirement from ^7.5.0 to ^8.0.0 (#375)
  • f7adb7a chore(deps): update @ commitlint/read requirement from ^7.1.2 to ^8.0.0 (#371)
  • 4105cea chore(deps): update @ commitlint/travis-cli requirement from ^7.5.0 to ^8.0.0 (#372)
  • d46915f chore(deps): update @ commitlint/load requirement from ^7.2.1 to ^8.0.0 (#373)
  • 6c52af4 chore(deps): update @ commitlint/cli requirement from ^7.5.0 to ^8.0.0 (#374)
  • f1c84f4 chore: release version v19.0.3
  • 77a7688 chore: update contributors
  • 8eba533 fix: fix gh release
  • 8e8088b chore: release version v19.0.2
  • 9fe3489 chore: update contributors
  • 4c2d5af chore: release version v19.0.1

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Server-side Request Forgery (SSRF)

@socket-security
Copy link

New dependency changes detected. Learn more about Socket for GitHub ↗︎

🚨 Potential security issues found in this pull request. To accept the risk, merge this PR and you will not be notified again.

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

📜 Install scripts

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Package Script field Source
[email protected] (added) postinstall examples/circuit-relaying/package.json via [email protected]
🫣 Native code

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

Package Location Source
[email protected] (added) binding.gyp examples/circuit-relaying/package.json via [email protected]
🍣 Git dependency

Contains a dependency which resolves to a remote git URL. Dependencies fetched from git URLs are not immutable can be used to inject untrusted code or reduce the likelihood of a reproducible install.

Publish the git dependency to npm or a private package repository and consume it from there.

Package Dependency Location Source
[email protected] (upgraded) karma-mocha-own-reporter@git+https://github.com/dryajov/karma-mocha-own-reporter.git#d562a92a12d5c76469a05d67cee19bcb8db22b23 package.json package.json via [email protected]
Pull request alert summary
Issue Status
Install scripts ⚠️ 1 issue
Native code ⚠️ 1 issue
Bin script shell injection ✅ 0 issues
Unresolved require ✅ 0 issues
Invalid package.json ✅ 0 issues
HTTP dependency ✅ 0 issues
Git dependency ⚠️ 1 issue
Potential typo squat ✅ 0 issues
Known Malware ✅ 0 issues
Telemetry ✅ 0 issues
Protestware/Troll package ✅ 0 issues

📊 Modified Dependency Overview:

⬆️ Updated Package Version Diff Capability Access +/- Transitive Count Publisher
[email protected] 14.0.0...20.6.1 network, filesystem, environment +322/-45 hugomrdias

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant