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

[Snyk] Security upgrade io.quarkus:quarkus-test-common from 2.14.0.Final to 3.14.1 #23

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sa-secrd
Copy link

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
low severity Information Disclosure
SNYK-JAVA-COMGOOGLEGUAVA-1015415
  486   io.quarkus:quarkus-test-common:
2.14.0.Final -> 3.14.1
Major version upgrade Proof of Concept
low severity Information Exposure
SNYK-JAVA-COMMONSCODEC-561518
  399   io.quarkus:quarkus-test-common:
2.14.0.Final -> 3.14.1
Major version upgrade No Known Exploit
low severity Creation of Temporary File in Directory with Insecure Permissions
SNYK-JAVA-COMGOOGLEGUAVA-5710356
  379   io.quarkus:quarkus-test-common:
2.14.0.Final -> 3.14.1
Major version upgrade No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Creation of Temporary File in Directory with Insecure Permissions

@backstage-rdstation
Copy link

A descrição do pull request fornecida não atende aos critérios estabelecidos. É importante escrever uma descrição que explique claramente o motivo da mudança e inclua instruções de teste. Uma boa descrição de pull request deve conter o contexto histórico, justificativa da mudança e passo a passo para testar a mudança. Isso ajuda a garantir uma comunicação eficaz e facilita a revisão do código.

Esse comentário foi gerado por inteligência artificial

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