- 
                Notifications
    
You must be signed in to change notification settings  - Fork 1
 
Update dependency postcss to v8.4.31 [SECURITY] #19
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
base: main
Are you sure you want to change the base?
Update dependency postcss to v8.4.31 [SECURITY] #19
Conversation
| 
           
  | 
    
| 
           Someone is attempting to deploy a commit to a Personal Account owned by @X-oss-byte on Vercel. @X-oss-byte first needs to authorize it.  | 
    
          
 | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Type: Enhancement
PR Summary: This pull request updates the postcss package from version 8.4.27 to 8.4.31. This update addresses a security vulnerability identified as CVE-2023-44270, which affects the parsing of   characters in CSS, potentially leading to the inclusion of parts of the CSS intended as comments in the PostCSS output. The update ensures that postcss and all related dependencies within the project are aligned with the patched version, mitigating the risk associated with the vulnerability.
Decision: Comment
📝 Type: 'Enhancement' - not supported yet.
- Sourcery currently only approves 'Typo fix' PRs.
 
✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.
No details provided.
✅ Small diff: the diff is small enough to approve with confidence.
No details provided.
General suggestions:
- Ensure thorough testing of CSS processing within the application to verify that the update does not introduce any regressions.
 - Consider setting up automated dependency update tools, if not already in place, to promptly address future security vulnerabilities.
 - Review other dependencies for potential security vulnerabilities and update them as necessary.
 
Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨
ccf7303    to
    232af48      
    Compare
  
    1860338    to
    db17405      
    Compare
  
    db17405    to
    8c8abc8      
    Compare
  
    8c8abc8    to
    8fce553      
    Compare
  
    8fce553    to
    2e96356      
    Compare
  
    f72e973    to
    6152e3b      
    Compare
  
    6152e3b    to
    c4b0d58      
    Compare
  
    c9c67f1    to
    e329972      
    Compare
  
    9f9edda    to
    4cc34d8      
    Compare
  
    a7c3107    to
    b9fbf84      
    Compare
  
    488b3f3    to
    dbeef8f      
    Compare
  
    dbeef8f    to
    7d1eae7      
    Compare
  
    
This PR contains the following updates:
8.4.27->8.4.31GitHub 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
\rdiscrepancies, 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.
Release Notes
postcss/postcss (postcss)
v8.4.31Compare Source
\rparsing to fix CVE-2023-44270.v8.4.30Compare Source
v8.4.29Compare Source
Node#source.offset(by Ido Rosenthal).v8.4.28Compare Source
Root.source.endfor better source map (by Romain Menke).Result.roottypes whenprocess()has no parser.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 becomes conflicted, 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.