Skip to content
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.

[Snyk] Security upgrade ejs from 3.0.1 to 3.1.6 #884

Closed
wants to merge 1 commit into from

Conversation

ofrobots
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:
    • packages/opencensus-exporter-zpages/package.json
    • packages/opencensus-exporter-zpages/package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 598/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 4.1
Arbitrary Code Injection
SNYK-JS-EJS-1049328
No Proof of Concept

(*) 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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

…census-exporter-zpages/package-lock.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-EJS-1049328
@google-cla
Copy link

google-cla bot commented Feb 10, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added the cla: no label Feb 10, 2021
@ofrobots
Copy link
Contributor Author

Curious - why is snyk bot posting as me? This is unexpected.

Maintainers: feel free to reject or approve the PR as appropriate. I don't have an opinion on this and didn't open the PR. I have revoked snyk access, but you may want to integrate it with the repo, if appropriate.

@aabmass
Copy link
Member

aabmass commented Feb 15, 2021

I'll recreated this PR as myself and close this. Weird

@aabmass aabmass closed this Feb 15, 2021
@aabmass aabmass mentioned this pull request Feb 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants