-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
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
chore(deps): update dependency postcss to v8.4.31 [security] #279
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/npm-postcss-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
✅ Deploy Preview for celo-composer ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected] |
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
from
February 25, 2024 10:10
b501747
to
49470a9
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
from
March 12, 2024 12:53
49470a9
to
09a83e1
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
2 times, most recently
from
March 24, 2024 15:42
e862f59
to
1f786f5
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
from
April 4, 2024 13:56
1f786f5
to
419d89a
Compare
renovate
bot
changed the title
chore(deps): update dependency postcss to v8.4.31 [security]
chore(deps): update dependency postcss to v8.4.31 [security] - autoclosed
Apr 18, 2024
renovate
bot
changed the title
chore(deps): update dependency postcss to v8.4.31 [security] - autoclosed
chore(deps): update dependency postcss to v8.4.31 [security]
Apr 19, 2024
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
from
April 19, 2024 06:50
419d89a
to
3fb9155
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
from
June 4, 2024 10:10
3fb9155
to
ebdddf0
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
from
July 12, 2024 06:19
ebdddf0
to
e7b97eb
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
from
August 6, 2024 05:54
e7b97eb
to
6558130
Compare
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.
This PR contains the following updates:
8.4.23
->8.4.31
GitHub Vulnerability Alerts
CVE-2023-44270
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.
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
References
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
postcss/postcss (postcss)
v8.4.31
Compare Source
\r
parsing to fix CVE-2023-44270.v8.4.30
Compare Source
v8.4.29
Compare Source
Node#source.offset
(by Ido Rosenthal).v8.4.28
Compare Source
Root.source.end
for better source map (by Romain Menke).Result.root
types whenprocess()
has no parser.v8.4.27
Compare Source
Container
clone methods types.v8.4.26
Compare Source
v8.4.25
Compare Source
v8.4.24
Compare Source
Plugin
types.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.