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 hexo-renderer-ejs from 1.0.0 to 2.0.0 #37

Closed
wants to merge 1 commit into from

Conversation

snyk-bot
Copy link
Contributor

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

merge advice

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

    • package.json
    • package-lock.json
  • Adding or updating a Snyk policy (.snyk) file; this file is required in order to apply Snyk vulnerability patches.
    Find out more.

Vulnerabilities that will be fixed

With an upgrade:
Severity Issue Breaking Change Exploit Maturity
medium severity Arbitrary Code Injection
SNYK-JS-EJS-1049328
Yes Proof of Concept
high severity Remote Code Execution (RCE)
SNYK-JS-EJS-2803307
Yes Proof of Concept
Commit messages
Package name: hexo-renderer-ejs The new version differs by 13 commits.

See the full diff

With a Snyk patch:
Severity Issue Exploit Maturity
medium severity Regular Expression Denial of Service (ReDoS)
npm:uglify-js:20151024
No Known Exploit

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:

🦉 Arbitrary Code Injection
🦉 Remote Code Execution (RCE)

@dimaslanjaka dimaslanjaka deleted the snyk-fix-43480b89f6bfa86493ad2e789dc37240 branch June 17, 2022 16:27
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.

2 participants