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.apicurio:apicurio-registry-utils-converter from 2.2.5.Final to 2.6.3.Final #24

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

Conversation

andersonsevla
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
high severity Denial of Service (DoS)
SNYK-JAVA-COMFASTERXMLJACKSONCORE-7569538
  649   io.apicurio:apicurio-registry-utils-converter:
2.2.5.Final -> 2.6.3.Final
No Known Exploit
high severity Infinite loop
SNYK-JAVA-ORGAPACHECOMMONS-6254296
  619   io.apicurio:apicurio-registry-utils-converter:
2.2.5.Final -> 2.6.3.Final
No Known Exploit
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JAVA-ORGAPACHECOMMONS-6254297
  429   io.apicurio:apicurio-registry-utils-converter:
2.2.5.Final -> 2.6.3.Final
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)
🦉 Allocation of Resources Without Limits or Throttling

@backstage-rdstation
Copy link

Esse pull request não atende aos critérios estabelecidos para uma boa descrição. É importante explicar claramente o motivo da mudança e incluir um passo a passo para testar o pull request. Uma boa descrição ajuda na compreensão e 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