[Security] Bump postcss from 8.4.29 to 8.4.32
Bumps postcss from 8.4.29 to 8.4.32. This update includes a security fix.
Vulnerabilities fixed
PostCSS line return parsing error An issue was discovered in PostCSS before 8.4.31. It affects linters using PostCSS to parse external Cascading Style Sheets (CSS). There may be
\r
discrepancies, as demonstrated by@font-face{ font:(\r/*);}
in a rule.This vulnerability affects linters using PostCSS to parse external untrusted CSS. An attacker can prepare CSS in such a way that it will contains parts parsed by PostCSS as a CSS comment. After processing by PostCSS, it will be included in the PostCSS output in CSS nodes (rules, properties) despite being originally included in a comment.
Patched versions: 8.4.31 Affected versions: < 8.4.31
Release notes
Sourced from postcss's releases.
8.4.32
- Fixed
postcss().process()
types (by@ferreira-tb
).8.4.31
- Fixed
\r
parsing to fix CVE-2023-44270.8.4.30
- Improved source map performance (by
@romainmenke
).
Changelog
Sourced from postcss's changelog.
8.4.32
- Fixed
postcss().process()
types (by Andrew Ferreira).8.4.31
- Fixed
\r
parsing to fix CVE-2023-44270.8.4.30
- Improved source map performance (by Romain Menke).
Commits
-
a0d9f10
Release 8.4.32 version -
0146b3e
Add Node.js 21 to CI -
2398534
Update dependencies -
1918533
Merge pull request #1902 from ferreira-tb/main -
395e6dc
FixProcessOptions
interface -
fa8cd15
Update dependencies -
199a7c4
Typo -
2528047
Update EM link -
90208de
Release 8.4.31 version -
58cc860
Fix carrier return parsing - Additional commits viewable in compare view
Dependabot commands
You can trigger Dependabot actions by commenting on this MR
-
$dependabot recreate
will recreate this MR rewriting all the manual changes and resolving conflicts