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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-44270US | medium5.3 | — | ||
An issue was discovered in PostCSS before 8.4.31. The vulnerability affects linters using PostCSS to parse external untrusted CSS. An attacker can prepare CSS in such a way that it… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/github/advisory-database/issues/2820WEB
- https://github.com/postcss/postcssPACKAGE
- https://github.com/postcss/postcss/blob/main/lib/tokenize.js#L25WEB
- https://github.com/postcss/postcss/commit/58cc860b4c1707510c9cd1bc1fa30b423a9ad6c5WEB
- https://github.com/postcss/postcss/releases/tag/8.4.31WEB
- https://lists.debian.org/debian-lts-announce/2024/12/msg00025.htmlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-44270ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan