Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Snyk] Fix for 7 vulnerabilities #435

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

Conversation

sa-secrd
Copy link

@sa-secrd sa-secrd commented Sep 6, 2024

snyk-top-banner

Snyk has created this PR to fix 7 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • backend/package.json
  • backend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Improper Input Validation
SNYK-JS-SOCKETIOPARSER-3091012
  704  
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-ANSIREGEX-1583908
  696  
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
  696  
high severity Denial of Service (DoS)
SNYK-JS-WS-7266574
  696  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-HTTPCACHESEMANTICS-3248783
  586  
low severity Prototype Pollution
SNYK-JS-MINIMIST-2429795
  506  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-3050818
  479  

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution
🦉 Improper Input Validation

@backstage-rdstation
Copy link

A descrição do pull request não foi encontrada nos resultados da pesquisa. Vamos analisar o texto fornecido para avaliar de acordo com os critérios estabelecidos.
O texto do pull request não atende aos critérios estabelecidos:

  1. Não explica claramente o motivo do pull request, apenas menciona que foi criado para corrigir vulnerabilidades nas dependências do projeto.
  2. Não inclui uma seção retratando o passo a passo ou as etapas necessárias para testar o pull request na prática.

É importante escrever uma descrição de pull request que explique o contexto histórico da mudança, a justificativa da mudança e inclua instruções de teste para garantir uma comunicação clara e eficaz.

Esse comentário foi gerado por inteligência artificial

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants