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

[Snyk] Security upgrade ejs from 3.1.7 to 3.1.10#8

Open
Geri76 wants to merge 1 commit intodistfrom
snyk-fix-4b6ef0a7ddca8b773c7123c259ef84b2
Open

[Snyk] Security upgrade ejs from 3.1.7 to 3.1.10#8
Geri76 wants to merge 1 commit intodistfrom
snyk-fix-4b6ef0a7ddca8b773c7123c259ef84b2

Conversation

@Geri76
Copy link
Owner

@Geri76 Geri76 commented Apr 29, 2024

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

✨ Snyk has automatically assigned this pull request, set who gets assigned.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

Changes included in this PR

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

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 551/1000
Why? Recently disclosed, Has a fix available, CVSS 5.3
Improper Control of Dynamically-Managed Code Resources
SNYK-JS-EJS-6689533
No No Known Exploit

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

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

👩‍💻 Set who automatically gets assigned

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Improper Control of Dynamically-Managed Code Resources

@Geri76 Geri76 self-assigned this Apr 29, 2024
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