[Snyk] Security upgrade @terra-money/terra.js from 3.0.6 to 3.0.10

[sascha1337]

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:
  • modules/testsuite/package.json
  • modules/testsuite/package-lock.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	701/1000 Why? Recently disclosed, Has a fix available, CVSS 8.3	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8172694	No	No Known Exploit
	828/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 8.7	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8187303	No	Proof of Concept

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

Commit messages

Package name: @terra-money/terra.js

The new version differs by 14 commits.

• bb65e95 chord(bip32): upgrade to make it avaiblable with node 17 (#249)
• f03a45a MsgInstantiateContract/MsgMigrateContract accepts string msg
• 51b2c86 build: bump version to 3.0.9
• 88bd751 feat: Add ClientUpdateProposal type.
• c677df4 add crisis/MsgVerifyInvariant
• 3608415 wasm query/execute accepts string params
• 6fe2b20 Update package.json
• a7a6abc docs: Replace links to the wiki (which is outdated).
• fcfc3b0 Fix/empty basic allowance (#236)
• d6c5476 Update README.md
• da1b344 build(deps): bump follow-redirects from 1.14.7 to 1.14.8
• 4233e49 fix: MsgInstantiateContract.Amino.admin can be empty (#228)
• 0af7525 Fix/basic allowance (#225)
• 5c0a18d fix comments for broadcastSync/Async

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@terra-money/[email protected]	Transitive: environment, eval, filesystem, network	+70	35.6 MB	hanjukim
npm/[email protected]	None	+7	954 kB	chai
npm/[email protected]	environment, filesystem	0	27.1 kB	motdotla
npm/[email protected]	environment, eval, filesystem Transitive: shell	+79	6.87 MB	juergba

🚮 Removed packages: npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Critical CVE	npm/[email protected]	CVE: GHSA-h755-8qp9-cq85 protobufjs Prototype Pollution vulnerability (CRITICAL) Affected versions: >= 6.10.0, < 6.11.4 Patched version: 6.11.4	modules/testsuite/package-lock.json modules/testsuite/package.json	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

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

• @SocketSecurity ignore npm/[email protected]