Skip to content

chore(deps): update dependency postcss to v8.4.31 [security] - #16

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-postcss-vulnerability
Open

chore(deps): update dependency postcss to v8.4.31 [security]#16
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-postcss-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Oct 10, 2023

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
postcss (source) 8.4.218.4.31 age confidence

PostCSS line return parsing error

CVE-2023-44270 / GHSA-7fh5-64p2-3v2j

More information

Details

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.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

postcss/postcss (postcss)

v8.4.31

Compare Source

v8.4.30

Compare Source

  • Improved source map performance (by Romain Menke).

v8.4.29

Compare Source

  • Fixed Node#source.offset (by Ido Rosenthal).
  • Fixed docs (by Christian Oliff).

v8.4.28

Compare Source

  • Fixed Root.source.end for better source map (by Romain Menke).
  • Fixed Result.root types when process() has no parser.

v8.4.27

Compare Source

  • Fixed Container clone methods types.

v8.4.26

Compare Source

  • Fixed clone methods types.

v8.4.25

Compare Source

v8.4.24

Compare Source

  • Fixed Plugin types.

v8.4.23

Compare Source

  • Fixed warnings in TypeDoc.

v8.4.22

Compare Source

  • Fixed TypeScript support with node16 (by Remco Haszing).

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/npm-postcss-vulnerability branch from c79181f to 26ff340 Compare November 6, 2023 11:47
@renovate
renovate Bot force-pushed the renovate/npm-postcss-vulnerability branch from 26ff340 to 682b0d4 Compare June 5, 2024 17:47
@renovate
renovate Bot force-pushed the renovate/npm-postcss-vulnerability branch from 682b0d4 to 02edb29 Compare December 4, 2024 00:01
@renovate
renovate Bot force-pushed the renovate/npm-postcss-vulnerability branch from 02edb29 to 319442a Compare March 12, 2025 04:03
@renovate
renovate Bot force-pushed the renovate/npm-postcss-vulnerability branch from 319442a to 6c6aab7 Compare March 21, 2025 00:12
@renovate
renovate Bot force-pushed the renovate/npm-postcss-vulnerability branch from 6c6aab7 to f985956 Compare August 14, 2025 23:22
@renovate
renovate Bot force-pushed the renovate/npm-postcss-vulnerability branch from f985956 to ce83d53 Compare September 26, 2025 07:33
@renovate
renovate Bot force-pushed the renovate/npm-postcss-vulnerability branch from ce83d53 to 66267e6 Compare February 13, 2026 19:43
@renovate
renovate Bot force-pushed the renovate/npm-postcss-vulnerability branch from 66267e6 to 9b89ba1 Compare May 1, 2026 11:13
@renovate
renovate Bot force-pushed the renovate/npm-postcss-vulnerability branch from 9b89ba1 to 58d3406 Compare July 18, 2026 03:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants