We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Dear SCSS-Tokenizer Team,
In scanning my node_modules for Regular Expression Denial of Service (ReDoS) Affecting org.webjars.npm:postcss and CVE-2021-23382
I encountered scss-tokenizer with previous-map.js with the same style regular expression that is cited in the CVE commit.
postcss
return sourceMapString.match(/\/\*\s*# sourceMappingURL=(.*)\*\//)[1].trim()
scss-tokenizer
let match = css.match(/\/\*\s*# sourceMappingURL=(.*)\s*\*\//)
It's slightly different, and maybe worth your time to double check.
I hope this helps.
The text was updated successfully, but these errors were encountered:
Do we have any blockers to merge the PR? Awaiting the CVE fix
Sorry, something went wrong.
Fixed in v0.4.3
Successfully merging a pull request may close this issue.
Dear SCSS-Tokenizer Team,
In scanning my node_modules for Regular Expression Denial of Service (ReDoS) Affecting org.webjars.npm:postcss and CVE-2021-23382
I encountered scss-tokenizer with previous-map.js with the same style regular expression that is cited in the CVE commit.
postcss
scss-tokenizer
It's slightly different, and maybe worth your time to double check.
I hope this helps.
The text was updated successfully, but these errors were encountered: