yurikrupnik / mussia8

Mussia8 base project monorepo poc for api gateway
alfred-lake.vercel.app
MIT License
0 stars 0 forks source link

[Snyk] Security upgrade swagger-ui-express from 4.1.6 to 4.2.0 #369

Open yurikrupnik opened 7 months ago

yurikrupnik commented 7 months ago

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: - packages/swagger/package.json - packages/swagger/package-lock.json #### Vulnerabilities that will be fixed ##### With an upgrade: Severity | Priority Score (*) | Issue | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:------------------------- ![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png "medium severity") | **591/1000**
**Why?** Proof of Concept exploit, Has a fix available, CVSS 5.4 | Server-side Request Forgery (SSRF)
[SNYK-JS-SWAGGERUIDIST-6056393](https://snyk.io/vuln/SNYK-JS-SWAGGERUIDIST-6056393) | No | Proof of Concept (*) 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 12 commits.
  • aa3d56a Bumped version of swagger-ui-dist and moved js template usage
  • ff10df4 Update README.md
  • fe789d8 Update README.md
  • d07439b Merge pull request #270 from jdgarcia/security-update
  • 9011cdf Merge pull request #269 from artyhedgehog/patch-1
  • e09c35f update swagger-ui-dist dependency to fix security vulnerabilities
  • de8e7eb readme: fix broken link to swagger-jsdoc
  • 5824af0 Merge pull request #236 from H3nSte1n/feature/Add_converage_section_to_readme
  • da7b5ff feat: Remove Coverage headline from README
  • b46e892 feat: Add coverage section to README
  • feb0664 Merge pull request #235 from tingstad/patch-1
  • 1699685 Update README - two swagger documents (typo)
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](https://app.snyk.io/org/yurikrupnik-plq/project/936ba291-3200-49b3-a0c0-39757102ec08?utm_source=github&utm_medium=referral&page=fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/yurikrupnik-plq/project/936ba291-3200-49b3-a0c0-39757102ec08?utm_source=github&utm_medium=referral&page=fix-pr/settings) 📚 [Read more about Snyk's upgrade and patch logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities) [//]: # (snyk:metadata:{"prId":"e312e53c-6a47-4e84-8ffc-692bda7d6105","prPublicId":"e312e53c-6a47-4e84-8ffc-692bda7d6105","dependencies":[{"name":"swagger-ui-express","from":"4.1.6","to":"4.2.0"}],"packageManager":"npm","projectPublicId":"936ba291-3200-49b3-a0c0-39757102ec08","projectUrl":"https://app.snyk.io/org/yurikrupnik-plq/project/936ba291-3200-49b3-a0c0-39757102ec08?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-JS-SWAGGERUIDIST-6056393"],"upgrade":["SNYK-JS-SWAGGERUIDIST-6056393"],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","priorityScore"],"priorityScoreList":[591],"remediationStrategy":"vuln"}) --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Server-side Request Forgery (SSRF)](https://learn.snyk.io/lesson/ssrf-server-side-request-forgery/?loc=fix-pr)
secure-code-warrior-for-github[bot] commented 7 months ago

Micro-Learning Topic: Server-side request forgery (Detected by phrase)

Matched on "Server-side Request Forgery"

What is this? (2min video)

Server-Side Request Forgery (SSRF) vulnerabilities are caused when an attacker can supply or modify a URL that reads or sends data to the server. The attacker can create a malicious request with a manipulated URL, when this request reaches the server, the server-side code executes the exploit URL causing the attacker to be able to read data from services that shouldn't be exposed.

Try a challenge in Secure Code Warrior