Security Threat - Update st from 1.10 to 1.2.2 #110
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
https://nvd.nist.gov/vuln/detail/CVE-2017-16224 GitHub's suggestion was to update st to version 1.2.2
|
This security related PR is open for some months now. Is this repository still maintained? |
|
This isn't exploitable at all, and only exists in a devDependency. The best course of action would be to silence the security warning. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update st from 1.10 to 1.2.2 to stop known security threat. Threat description: https://nvd.nist.gov/vuln/detail/CVE-2017-16224
I receive weekly emails from GitHub about st's version number having a known security threat.
GitHub's suggestion was to update st to it's latest version, 1.2.2.
Thank you for your time,
Barret
forwarding from
ISSUE: rstudio/leaflet#585
PR: rstudio/leaflet#575