Blackduck: Automated PR: Update fsevents/1.2.9 to 1.2.13 #131
Conversation
This file contains hidden or 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
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.
Vulnerabilities associated with fsevents/1.2.9
BDSA-2023-1218 (HIGH): fsevents npm package is vulnerable to hijacking due to malicious code run during installation via a hijacked URL in the install configuration. This would allow the current owner of the URL to run code of their choosing on each installation of the package.
Note: Originally, the credentials to the S3 bucket of the affected URL were lost. It was demonstrated by a security researcher that the bucket became available to register once again, and it was taken over by the researcher to demonstrate possible impact of this vulnerability. At this time, AWS has taken possession of the S3 bucket and currently blocks all access, neutralizing any threat. Should this bucket become available to use in the future, affected versions of fsevents will once again become vulnerable. This occurred in August 2023, when the bucket was briefly reinstated in error.
Click Here To See More Details On Server