Fix CVE–2022–25858#12
Open
debricked-staging[bot] wants to merge 1 commit intodevelopfrom
Open
Conversation
debricked-staging
Bot
force-pushed
the
debricked-fix-CVE_2022_25858-2115f2278938e169
branch
from
ff1d6d8 to
92c01db
Compare
debricked-staging
Bot
force-pushed
the
debricked-fix-CVE_2022_25858-2115f2278938e169
branch
from
92c01db to
e50f167
Compare
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.
CVE–2022–25858
Vulnerable dependency: terser (npm)
4.8.0
Vulnerability details
Description
NVD
GitHub
CVSS details -
7.5
References
NVD - CVE-2022-25858
THIRD PARTY
backport fix to potential regexp DDOS · terser/terser@d8cc569 · GitHub
fix potential regexp DDOS · terser/terser@a4da734 · GitHub
terser/evaluate.js at master · terser/terser · GitHub
Terser insecure use of regular expressions before v4.8.1 and v5.14.2 leads to ReDoS · CVE-2022-25858 · GitHub Advisory Database · GitHub
Related information
📌 Remember! Check the changes to ensure they don't introduce any breaking changes.
📚 Read more about the CVE