Skip to content

[Snyk] Security upgrade aegir from 14.0.0 to 31.0.0 #184

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
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-JS-ANSIREGEX-1583908
Yes Proof of Concept
medium severity 636/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.3
Prototype Pollution
SNYK-JS-DOTPROP-543489
Yes Proof of Concept
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-JS-TRIMNEWLINES-1298042
Yes No Known Exploit
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Regular Expression Denial of Service (ReDoS)
npm:debug:20170905
Yes Proof of Concept
medium severity 469/1000
Why? Has a fix available, CVSS 5.1
Denial of Service (DoS)
npm:mem:20180117
Yes No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Regular Expression Denial of Service (ReDoS)
npm:ms:20170412
Yes No Known Exploit

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

Commit messages
Package name: aegir The new version differs by 250 commits.
  • 6bd6e1c chore: release version v31.0.0
  • c58424f chore: update contributors
  • 059290f release v31 (#737)
  • 4002b50 feat: copy .d.ts. to dist (#738)
  • 9f67cb9 feat: upgrade linter to v2.0.0
  • 846bb25 feat: ts, build, docs and lint improvements (#732)
  • 1212314 fix: upgrade karma (#733)
  • 3d54004 feat: rename --ts flag to --ts-repo and fix ts repo support (#730)
  • 1149281 feat: update typedoc and improvemnts to docs cmd (#727)
  • 9b7136a fix: fix docs paths and update deps (#726)
  • d543f83 docs: typesVersions workaround (#717)
  • 3105a76 chore: release version v30.3.0
  • a2059cd chore: update contributors
  • 659598b feat: support vendored types and improvements to build and ts cmds (#705)
  • 182ac81 chore: release version v30.2.0
  • 148c4ba chore: update contributors
  • 843baef fix: prepare scripts when aegir gets hoisted (#702)
  • 66fb479 chore: release version v30.1.0
  • 5d6bd34 chore: update contributors
  • 9d8a508 feat: add utils types (#701)
  • cde621d chore: fix publish
  • a093b4a chore: release version v30.0.0
  • 772797e chore: update contributors
  • 5f55cba feat: upgrade ts to 4.1.x (#689)

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution

@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) install examples/circuit-relaying/package.json via [email protected]
[email protected] (added) postinstall examples/circuit-relaying/package.json via [email protected]
[email protected] (added) postinstall examples/circuit-relaying/package.json via [email protected]
[email protected] (added) postinstall examples/circuit-relaying/package.json via [email protected]
Pull request alert summary
Issue Status
Install scripts ⚠️ 4 issues
Native code ✅ 0 issues
Bin script shell injection ✅ 0 issues
Unresolved require ✅ 0 issues
Invalid package.json ✅ 0 issues
HTTP dependency ✅ 0 issues
Git dependency ✅ 0 issues
Potential typo squat ✅ 0 issues
Known Malware ✅ 0 issues
Telemetry ✅ 0 issues
Protestware/Troll package ✅ 0 issues

📊 Modified Dependency Overview:

⬆️ Updated Package Version Diff Added Capability Access +/- Transitive Count Publisher
[email protected] 14.0.0...31.0.4 environment +376/-46 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