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 software.amazon.awssdk:kinesis from 2.13.13 to 2.25.63 #8

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

Conversation

fsrocha-dev
Copy link

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


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

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

Snyk changed the following file(s):

  • debezium-server/debezium-server-bom/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JAVA-IONETTY-6483812
  586   software.amazon.awssdk:kinesis:
2.13.13 -> 2.25.63
Proof of Concept

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:

🦉 Allocation of Resources Without Limits or Throttling

@backstage-rdstation
Copy link

Olá!

Obrigado por enviar o pull request. No entanto, sua descrição não atende aos critérios estabelecidos para uma boa descrição de pull request.

Para melhorar, sugiro que você inclua uma explicação clara do motivo do pull request estar sendo feito, incluindo o contexto histórico, justificativa ou racional da mudança. Além disso, seria interessante adicionar uma seção com o passo a passo ou as etapas necessárias para testar o pull request na prática.

Escrever uma boa descrição de pull request é importante para garantir que os revisores entendam o que está sendo proposto e como testar as mudanças. Espero que essas dicas sejam úteis para seus próximos pull requests.

Fico à disposição para ajudar em caso de dúvidas.

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