Skip to content
This repository was archived by the owner on Aug 30, 2024. It is now read-only.

Comments

[Snyk] Security upgrade swagger-ui-express from 4.2.0 to 4.3.0#105

Open
Fadyio wants to merge 1 commit intomainfrom
snyk-fix-cde6726605968e0c9e78e9d4a2c3600f
Open

[Snyk] Security upgrade swagger-ui-express from 4.2.0 to 4.3.0#105
Fadyio wants to merge 1 commit intomainfrom
snyk-fix-cde6726605968e0c9e78e9d4a2c3600f

Conversation

@Fadyio
Copy link
Owner

@Fadyio Fadyio commented May 9, 2024

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


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • backend/package.json
    • backend/package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 663/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.4
Server-side Request Forgery (SSRF)
SNYK-JS-SWAGGERUIEXPRESS-6815423
No Proof of Concept
medium severity 727/1000
Why? Mature exploit, Recently disclosed, Has a fix available, CVSS 5.4
Server-side Request Forgery (SSRF)
SNYK-JS-SWAGGERUIEXPRESS-6815424
No Mature

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: swagger-ui-express The new version differs by 1 commits.
  • 512970a bump version of swagger-ui-dist due to security update

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Server-side Request Forgery (SSRF)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants