react-ssr-starter
                                
                                
                                
                                    react-ssr-starter copied to clipboard
                            
                            
                            
                        🚨 [security] Update serve-static 1.14.2 → 1.16.2 (minor)
🚨 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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ serve-static (1.14.2 → 1.16.2) · Repo · Changelog
Security Advisories 🚨
🚨 serve-static vulnerable to template injection that can lead to XSS
Impact
passing untrusted user input - even after sanitizing it - to
redirect()may execute untrusted codePatches
this issue is patched in serve-static 1.16.0
Workarounds
users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist
Details
successful exploitation of this vector requires the following:
- The attacker MUST control the input to response.redirect()
 - express MUST NOT redirect before the template appears
 - the browser MUST NOT complete redirection before:
 - the user MUST click on the link in the template
 
Release Notes
1.16.0
What's Changed
- Remove link renderization in html while redirecting (#173)
 New Contributors
- @UlisesGascon made their first contribution in #173
 Full Changelog: v1.15.0...1.16.0
1.15.0
- deps: [email protected]
 
- Fix emitted 416 error missing headers property
 - Limit the headers removed for 304 response
 - deps: [email protected]
 - deps: [email protected]
 - deps: [email protected]
 - deps: [email protected]
 - deps: [email protected]
 
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 22 commits:
1.16.2fix(deps): encodeurl@~2.0.01.16.1fix(deps): [email protected]1.16.0Merge commit from fork1.15.0docs: update CI linkbuild: [email protected]deps: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: [email protected]build: remove package-lock
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)