🚨 [security] Update nuxt 2.16.3 → 3.12.4 (major)
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ nuxt (2.16.3 → 3.12.4) · Repo
Security Advisories 🚨
🚨 nuxt vulnerable to Cross-site Scripting in navigateTo if used after SSR
Summary
The
navigateTofunction attempts to blockthejavascript:protocol, but does not correctly use API's provided byunjs/ufo. This library also contains parsing discrepancies.Details
The function first tests to see if the specified URL has a protocol. This uses the unjs/ufo package for URL parsing. This function works effectively, and returns true for a
javascript:protocol.After this, the URL is parsed using the
parseURLfunction. This function will refuse to parse poorly formatted URLs. Parsingjavascript:alert(1)returns null/"" for all values.Next, the protocol of the URL is then checked using the
isScriptProtocolfunction. This function simply checks the input against a list of protocols, and does not perform any parsing.The combination of refusing to parse poorly formatted URLs, and not performing additional parsing means that script checks fail as no protocol can be found. Even if a protocol was identified, whitespace is not stripped in the
parseURLimplementation, bypassing theisScriptProtocolchecks.Certain special protocols are identified at the top of
parseURL. Inserting a newline or tab into this sequence will block the special protocol check, and bypass the latter checks.PoC
POC - https://stackblitz.com/edit/nuxt-xss-navigateto?file=app.vue
Attempt payload X, then attempt payload Y.
Impact
XSS, access to cookies, make requests on user's behalf.
Recommendations
As always with these bugs, the
URLconstructor provided by the browser is always the safest method of parsing a URL.Given the cross-platform requirements of nuxt/ufo a more appropriate solution is to make parsing consistent between functions, and to adapt parsing to be more consistent with the WHATWG URL specification.
Note
I've reported this vulnerability here as it is unclear if this is a bug in ufo or a misuse of the ufo library.
This ONLY has impact after SSR has occured, the
javascript:protocol within a location header does not trigger XSS.
🚨 nuxt Code Injection vulnerability
he Nuxt dev server between versions 3.4.0 and 3.4.3 is vulnerable to code injection when it is exposed publicly.
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
✳️ autoprefixer (10.4.14 → 10.4.19) · Repo · Changelog
Release Notes
10.4.19
- Removed
end value has mixed support, consider using flex-endwarning sinceend/startnow have good support.
10.4.18
- Fixed removing
-webkit-box-orienton-webkit-line-clamp(@Goodwine).
10.4.17
- Fixed
user-select: containprefixes.
10.4.16
- Improved performance (by @romainmenke).
- Fixed docs (by @coliff).
10.4.15 (from changelog)
- Fixed
::backdropprefixes (by 一丝).- Fixed docs (by Christian Oliff).
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 33 commits:
Release 10.4.19 versionRemove end→flex-end warningUpdate dependenciesMove to flat ESLint configUpdate dependenciesRelease 10.4.18 versionUpdate dependenciesUpdate c8 configAdd Node.js 21 to CIAutomate release creationUpdate actionsPreserve -webkit-box-orient when -webkit-line-clamp is present (#1511)Release 10.4.17 versionUpdate dependenciesFix user-select: containUpdate dependenciesRelease 10.4.16 versionUpdate dependenciesUpdate CIimprove performance (#1500)Update dependenciesRemove deprecated browsers from README (#1499)Release 10.4.15 versionRun tests in parallelUpdate dependenciesfeat: `::backdrop` using `@mdn/browser-compat-data` (#1498)Update dependencies and code styleMove to pnpm 8Use Node.js 20 on CILock pnpmUpdate dependenciesAdd funding optionHTTPS and update URLS in README (#1494)
✳️ postcss (8.4.21 → 8.4.40) · Repo · Changelog
Security Advisories 🚨
🚨 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
\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
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
- @depfu rebase
- Rebases against your default branch and redoes this update
- @depfu recreate
- Recreates this PR, overwriting any edits that you've made to it
- @depfu merge
- Merges this PR once your tests are passing and conflicts are resolved
- @depfu cancel merge
- Cancels automatic merging of this PR
- @depfu close
- Closes this PR and deletes the branch
- @depfu reopen
- Restores the branch and reopens this PR (if it's closed)
- @depfu pause
- Ignores all future updates for this dependency and closes this PR
- @depfu pause [minor|major]
- Ignores all future minor/major updates for this dependency and closes this PR
- @depfu resume
- Future versions of this dependency will create PRs again (leaves this PR as is)