-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update dependency webpack-dev-server to v3 [SECURITY] #16
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-webpack-dev-server-vulnerability
base: master
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
renovate
bot
changed the title
Pin dependency webpack-dev-server to v1.16.5 [SECURITY]
Pin dependency webpack-dev-server to 1.16.5 [SECURITY]
May 9, 2021
renovate
bot
changed the title
Pin dependency webpack-dev-server to 1.16.5 [SECURITY]
Pin dependency webpack-dev-server to v1.16.5 [SECURITY]
May 15, 2021
renovate
bot
changed the title
Pin dependency webpack-dev-server to v1.16.5 [SECURITY]
Pin dependency webpack-dev-server to v [SECURITY]
Mar 7, 2022
renovate
bot
changed the title
Pin dependency webpack-dev-server to v [SECURITY]
Pin dependency webpack-dev-server to v1.16.5 [SECURITY]
Sep 25, 2022
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
November 20, 2022 15:33
e237ec3
to
05fd871
Compare
renovate
bot
changed the title
Pin dependency webpack-dev-server to v1.16.5 [SECURITY]
Update dependency webpack-dev-server to v4 [SECURITY]
Nov 20, 2022
renovate
bot
changed the title
Update dependency webpack-dev-server to v4 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Mar 27, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
March 27, 2023 16:53
05fd871
to
fae32cb
Compare
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
May 29, 2023 17:53
fae32cb
to
cd50edc
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v4 [SECURITY]
May 29, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
June 1, 2023 16:09
cd50edc
to
f09f323
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v4 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Jun 1, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
June 8, 2023 06:00
f09f323
to
04129a9
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v4 [SECURITY]
Jun 8, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
June 10, 2023 11:19
04129a9
to
e7c47fc
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v4 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Jun 10, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
June 14, 2023 02:27
e7c47fc
to
b9e917d
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v4 [SECURITY]
Jun 14, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
June 17, 2023 05:21
b9e917d
to
899fbd0
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v4 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Jun 17, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
June 18, 2023 11:58
899fbd0
to
694f0e5
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v4 [SECURITY]
Jun 18, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
June 22, 2023 23:12
694f0e5
to
2f2aa89
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v4 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Jun 22, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
June 30, 2023 02:33
2f2aa89
to
f522784
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v4 [SECURITY]
Jun 30, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
July 1, 2023 00:46
f522784
to
30d7dfe
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v4 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Jul 1, 2023
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
July 7, 2023 20:41
30d7dfe
to
6990797
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v4 [SECURITY]
Jul 7, 2023
renovate
bot
changed the title
Update dependency webpack-dev-server to v5 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Oct 11, 2024
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
October 29, 2024 23:48
418602f
to
9098141
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v5 [SECURITY]
Oct 29, 2024
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
October 31, 2024 05:42
9098141
to
a5fe96a
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v5 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Oct 31, 2024
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
December 3, 2024 05:46
a5fe96a
to
94e87b9
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v5 [SECURITY]
Dec 3, 2024
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
December 6, 2024 05:29
94e87b9
to
2216ab9
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v5 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Dec 6, 2024
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
December 19, 2024 02:59
2216ab9
to
7efb1f0
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v5 [SECURITY]
Dec 19, 2024
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
December 21, 2024 20:44
7efb1f0
to
4b27d6b
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v5 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Dec 21, 2024
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
December 24, 2024 17:51
4b27d6b
to
98e71f3
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v5 [SECURITY]
Dec 24, 2024
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
December 25, 2024 20:35
98e71f3
to
456f6a1
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v5 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Dec 25, 2024
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
January 15, 2025 19:49
456f6a1
to
9d9ca83
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v5 [SECURITY]
Jan 15, 2025
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
January 17, 2025 03:52
9d9ca83
to
c73dab8
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v5 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Jan 17, 2025
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
January 25, 2025 08:08
c73dab8
to
0d4c9ce
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v5 [SECURITY]
Jan 25, 2025
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
January 26, 2025 06:56
0d4c9ce
to
dd4cb9a
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v5 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Jan 26, 2025
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
January 31, 2025 07:44
dd4cb9a
to
2a96866
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v3 [SECURITY]
Update dependency webpack-dev-server to v5 [SECURITY]
Jan 31, 2025
renovate
bot
force-pushed
the
renovate/npm-webpack-dev-server-vulnerability
branch
from
February 1, 2025 18:23
2a96866
to
938b273
Compare
renovate
bot
changed the title
Update dependency webpack-dev-server to v5 [SECURITY]
Update dependency webpack-dev-server to v3 [SECURITY]
Feb 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
^1.14.0
->^3.1.11
GitHub Vulnerability Alerts
CVE-2018-14732
Versions of
webpack-dev-server
before 3.1.10 are missing origin validation on the websocket server. This vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement (HMR) are not validated.Recommendation
For
webpack-dev-server
update to version 3.1.11 or later.Release Notes
webpack/webpack-dev-server (webpack-dev-server)
v3.1.11
Compare Source
Bug Fixes
options.color
) (#1555) (55398b5)spdy
v3.4.1...4.0.0 (assertion error) (#1491) (#1563) (7a3a257)node
version checks (#1543) (927a2b3)v3.1.10
Compare Source
Bug Fixes
writeToDisk
option to schema (#1520) (d2f4902)sockjs-client
v1.1.5...1.3.0 (url-parse
vulnerability) (#1537) (e719959)tls.DEFAULT_ECDH_CURVE
to'auto'
(#1531) (c12def3)v3.1.9
Compare Source
3.1.9 (2018-09-24)
v3.1.8
Compare Source
Bug Fixes
yargs
security vulnerability (dependencies
) (#1492) (8fb67c9)quiet
always takes precedence (options.quiet
) (#1486) (7a6ca47)v3.1.7
Compare Source
Bug Fixes
spdy
onnode >= v10.0.0
(#1451) (8ab9eb6)v3.1.6
Compare Source
Bug Fixes
process
signals correctly when the server isn't ready yet (#1432) (334c3a5)open-page
example (#1401) (df30727)output
filename to be a{Function}
(#1409) (e2220c4)v3.1.5
Compare Source
Progress
event in the client so plugins can use it (#1427)sockjs-client
to fix infinite reconnection loop (#1434)v3.1.4
Compare Source
logLevel
optionsilent
not being accepted by schema validation (#1372)v3.1.3
Compare Source
v3.1.2
Compare Source
v3.1.1
Compare Source
Bug Fixes
v3.1.0
Compare Source
Updates
webpack-log
is now used for logging to the terminal (webpack-dev-middleware was already using this).logLevel
option is added for more fine-grained control over the logging.Bugfixes
v3.0.0
Compare Source
Updates
Bugfixes
Huge thanks to all the contributors!
Please note that webpack-serve will eventually be the successor of webpack-dev-server. The core features already work so if you're brave enough give it a try!
v2.11.5
Compare Source
v2.11.4
Compare Source
v2.11.3
Compare Source
v2.11.2
Compare Source
v2.11.1
Compare Source
Our third attempt to fix compatibility with old browsers (#1273), this time we'll get it right.
v2.11.0
Compare Source
Version 2.11.0 adds the transpilation of the client scripts via babel to ES5 which restores backwards compatibility (that was removed in 2.8.0) to very old or out of date browsers.
v2.10.1
Compare Source
v2.10.0
Compare Source
Version 2.10.0 adds the transpilation of the client scripts via babel to ES5 which restores backwards compatibility (that was removed in 2.8.0) to very old or out of date browsers.
Important webpack-dev-server has entered a maintenance-only mode. We won't be accepting any new features or major modifications. We'll still welcome pull requests for fixes however, and will continue to address any bugs that arise. Announcement with specifics pending.
Bugfixes
reportTime
option (#1209)Updates
ce30460
)marked
version for ReDos vuln (#1255)v2.9.7
Compare Source
v2.9.6
Compare Source
Bugfixes
v2.9.5
Compare Source
Updates
6b2d7a0
)v2.9.4
Compare Source
Bugfixes
v2.9.3
Compare Source
Bugfixes
sockjs-client
instead of module source (#1148)v2.9.2
Compare Source
Bugfixes
Changed property descriptor for Array.includes polyfill (#1134)
Updates
Remove header additional property validation (#1115)
Allow explicitly setting the protocol from the public option (#1117)
Updates readme with support, usage, and caveats (outlines no support for old IE)
v2.9.1
Compare Source
Patch release to resolve an errant log message in
setup
v2.9.0
Compare Source
Note: Minor release due to addition of
before
andafter
hooksFeatures
Deprecate setup in favor of before and after hooks (#1108)
Bugfixes
Fixed check for webpack/hot/log when setting HMR log level. (#1096)
fixes #1109: internal-ip update breaks useLocalIp option
Fix quote style to satisfy ESLint (#1098)
Updates
Made error overlay translucent. (#1097)
v2.8.2
Compare Source
Bugfixes
fixes #1087: yargs@8 causes error output with webpack@2.x
fixes #1084: template literals causing errors on IE (#1089) …
fixes #1086: promise configs fix and example
Updates
add promise-config example
v2.8.1
Compare Source
Bugfixes
fixes #1081, closes #1079. addDevServerEndpoints needs app stub for createDomain
fixes #1080 - jQuery update caused live bundle iframe issue
clean up progress option typo and options def
v2.8.0
Compare Source
Features
Bugfixes
Updates
--open
option to specify the browser to use (#825)subjectAltName
field in self-signed cert (#987)v2.7.1
Compare Source
v2.6.1
Compare Source
loglevel
from devDependencies to dependencies #1001v2.6.0
Compare Source
clientLogLevel
(#921).quiet
is set totrue
(#970).--disable-host-check
(#980).v2.5.1
Compare Source
Bugfixes
Fix peer dependencies to support webpack 3 ( #946 ) ( Fixes #932 )
v2.5.0
Compare Source
Security
Don't provide a SSL cert, but generate one on demand. Unique for each developer.
https://medium.com/[@​mikenorth/961572624c54](https://redirect.github.com/mikenorth/961572624c54) by Mike North
Bugfixes
allowedHosts
optionopenPage
option to open a specific page--bonjour
lan
option, which listen on lan ip by defaultv2.4.5
Compare Source
Bugfixes
v2.4.4
Compare Source
Bugfixes:
disableHostCheck
to schemav2.4.3
Compare Source
Security fix:
This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.
We added a check for the correct
Host
header to the webpack-dev-server.This allowed evil websites to access your assets.
The
Host
header of the request have to match the listening adress or the host provided in thepublic
option.Make sure to provide correct values here.
The response will contain a note when using an incorrect
Host
header.For usage behind a Proxy or similar setups we also added a
disableHostCheck
option to disable this check.Only use it when you know what you do. Not recommended.
This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2
Note: This only affect the development server and middleware. webpack and built bundles are not affected.
Credits to Ed Morley from Mozilla for reporting the issue.
Bugfixes:
Host
doesn't match listening host orpublic
option.localhost
or127.0.0.1
are not blocked.Features:
disableHostCheck
option to disable the host checkv2.4.2
Compare Source
entry
not working when it was a function (#802).contentBase
as an array did not work when used via CLI (#832).v2.4.1
Compare Source
3cb79bd
).v2.4.0
Compare Source
contentBase: false
in combination with thehistoryApiFallback
option threw an error (#791).--open
fails to open the browser (#780).overlay
option to also show compiler warnings (off by default) (#790):v2.3.0
Compare Source
overlay: true
to enable (#764)!--open
andoptions.public
, the browser will now open the same URL as you have defined inpublic
(#749).options.port
now allows strings to be passed in, previously only integers were accepted (#766).v2.2.1
Compare Source
v2.2.0
Compare Source
First webpack-dev-server 2 release
Following the webpack 2 release.
It's equal to the last RC.
If you're curious about the highlights, read this fancy Medium post.
v1.16.5
Compare Source
v1.16.4
Compare Source
Security fix:
This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.
We added a check for the correct
Host
header to the webpack-dev-server.This allowed evil websites to access your assets.
The
Host
header of the request have to match the listening adress or the host provided in thepublic
option.Make sure to provide correct values here.
The response will contain a note when using an incorrect
Host
header.For usage behind a Proxy or similar setups we also added a
disableHostCheck
option to disable this check.Only use it when you know what you do. Not recommended.
This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2
Note: This only affect the development server and middleware. webpack and built bundles are not affected.
Credits to Ed Morley from Mozilla for reporting the issue.
Bugfixes:
Host
doesn't match listening host orpublic
option.localhost
or127.0.0.1
are not blocked.Features:
disableHostCheck
option to disable the host checkv1.16.3
Compare Source
Probably the last release in the v1.x range:
Promise
.v1.16.2
Compare Source
bypass
feature (#614).v1.16.1
Compare Source
v1.16.0
Compare Source
clientLogLevel
(--client-log-level
for CLI) option. It controls the log messages shown in the browser. Available levels areerror
,warning
,info
ornone
(#579).v1.15.2
Compare Source
v1.15.1
Compare Source
bypass
config option for proxies (#563).*
as a proxy wildcard.document
when using inline modus (#577).v1.15.0
Compare Source
--stdin
flag, to close the dev server on process exit (#352).--open
flag to open a browser pointing to the server (#329).--public
flag to override the url used for connecting to the web socket (#368).options.contentBase
, so multiple sources are allowed (#374).options.staticOptions
to allow passing through Express static options (#385).--cacert
flag not doing anything (#532).v1.14.1
Compare Source
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.