Skip to content
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

fix(Snyk): Security upgrade @google-cloud/translate from 6.3.1 to 7.0.0 #92

Closed

Conversation

mayrbenjamin92
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


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

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 823/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 8.6
Prototype Pollution
SNYK-JS-PROTOBUFJS-5756498
Yes Proof of Concept

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

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:

🦉 Prototype Pollution

@XavierJordaMurria XavierJordaMurria changed the title [Snyk] Security upgrade @google-cloud/translate from 6.3.1 to 7.0.0 fix(Snyk): Security upgrade @google-cloud/translate from 6.3.1 to 7.0.0 Jul 19, 2023
@XavierJordaMurria
Copy link
Collaborator

update it in another pr

@mayrbenjamin92 mayrbenjamin92 deleted the snyk-fix-2f171f1a6ec84067ecc20d44aff24313 branch April 26, 2024 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants