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] Fix for 1 vulnerabilities #19

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

Conversation

fsrocha-dev
Copy link

snyk-top-banner

Snyk has created this PR to fix 1 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
high severity Denial of Service (DoS)
SNYK-JAVA-COMFASTERXMLJACKSONCORE-7569538
  721   com.fasterxml.jackson.core:jackson-core:
2.13.3 -> 2.15.0
com.fasterxml.jackson.core:jackson-databind:
2.13.3 -> 2.15.0
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:
2.13.3 -> 2.15.0
org.apache.kafka:connect-json:
3.3.1 -> 3.7.0
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:

🦉 Denial of Service (DoS)

@backstage-rdstation
Copy link

Olá!

Obrigado por enviar o pull request para corrigir uma vulnerabilidade nas dependências do Maven. No entanto, para melhorar a descrição do seu pull request, sugiro adicionar mais informações.

Você poderia explicar de forma clara o motivo dessa correção ser necessária, incluindo o contexto histórico da mudança, a justificativa da mudança ou o racional por trás dela. Além disso, seria útil incluir um passo a passo ou instruções de teste para que os revisores possam testar o pull request na prática.

Essas informações adicionais ajudarão a tornar a descrição do seu pull request mais completa e compreensível para todos os envolvidos. Obrigado pela colaboração!

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