Closed dependabot[bot] closed 2 months ago
This issue probably doesn't affect us. It's in a Web server framework, which we use only within some dev dependencies:
$ yarn why serve-static
yarn why v1.22.19
[1/4] Why do we have the module "serve-static"...?
[…]
=> Found "serve-static@1.15.0"
info Reasons this module exists
- "react-native#@react-native-community#cli" depends on it
- Hoisted from "react-native#@react-native-community#cli#serve-static"
- Hoisted from "react-native#@react-native-community#cli#@react-native-community#cli-debugger-ui#serve-static"
- Hoisted from "react-native#@react-native-community#cli#@react-native-community#cli-server-api#serve-static"
[…]
Apparently the vulnerability shows up if an attacker makes a request to the server, and the server code calls response.redirect
.
I'm not certain it can't affect us, though: possibly @react-native-community/cli-debugger-ui
via serve-static
does expose such a redirect, so that if someone's running that when developing our codebase possibly it could be accessible to an attacker on another machine, or something.
So we'll take the upgrade.
The diff is a little messy as I commented above. The mess is harmless but would probably cause similar mess in reverse the next time we do a yarn upgrade
or yarn add
etc. operation ourselves; possibly even just yarn
/ yarn install
(which is routine in development). So I'll take a few extra minutes and do the upgrade myself.
So I'll take a few extra minutes and do the upgrade myself.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version
or @dependabot ignore this minor version
.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
(Apart from the upgrade itself which is of possible but doubtful relevance, this PR came in handy because it turned up #5888! That's something we'll definitely want to fix.)
I'm not certain it can't affect us, though: possibly […]
Also to be explicit about why I gave this more attention than #5874: that one was a DoS, but this one (CVE-2024-43800) is RCE if it can be triggered, which is a much worse consequence.
Bumps serve-static from 1.15.0 to 1.16.2.
Release notes
Sourced from serve-static's releases.
Changelog
Sourced from serve-static's changelog.
Commits
ec9c5ec
1.16.2f454d37
fix(deps): encodeurl@~2.0.077a8255
1.16.14263f49
fix(deps): send@0.19.048c7397
1.16.00c11fad
Merge commit from forkMaintainer changes
This version was pushed to npm by wesleytodd, a new releaser for serve-static since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show