webpack-dev-server@3.1.14 getting Missing Origin Validation while using npm audit
I have update the webpack-dev-server to the latest 3.1.14 but I am still getting vulnerability issue while using npm audit --fix. I have tries every thing. cleaning cache. clearing all modules and install again but all same.
Following is the error when I run npm audit
$ npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Missing Origin Validation
Package webpack-dev-server
Patched in >=3.1.11
Dependency of webpack-dev-server [dev]
Path webpack-dev-server
More info https://nodesecurity.io/advisories/725
found 1 high severity vulnerability in 60688 scanned packages
1 vulnerability requires manual review. See the full report for details.
security webpack-dev-server npm-audit
asked Jan 2 at 10:18
ma_dev_15ma_dev_15
409211
add a comment |
I have update the webpack-dev-server to the latest 3.1.14 but I am still getting vulnerability issue while using npm audit --fix. I have tries every thing. cleaning cache. clearing all modules and install again but all same.
Following is the error when I run npm audit
$ npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Missing Origin Validation
Package webpack-dev-server
Patched in >=3.1.11
Dependency of webpack-dev-server [dev]
Path webpack-dev-server
More info https://nodesecurity.io/advisories/725
found 1 high severity vulnerability in 60688 scanned packages
1 vulnerability requires manual review. See the full report for details.
security webpack-dev-server npm-audit
asked Jan 2 at 10:18
ma_dev_15ma_dev_15
409211
It is fixed by npm now.. RESOLVED
– ma_dev_15
Jan 3 at 3:39
add a comment |
I have update the webpack-dev-server to the latest 3.1.14 but I am still getting vulnerability issue while using npm audit --fix. I have tries every thing. cleaning cache. clearing all modules and install again but all same.
Following is the error when I run npm audit
$ npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Missing Origin Validation
Package webpack-dev-server
Patched in >=3.1.11
Dependency of webpack-dev-server [dev]
Path webpack-dev-server
More info https://nodesecurity.io/advisories/725
found 1 high severity vulnerability in 60688 scanned packages
1 vulnerability requires manual review. See the full report for details.
security webpack-dev-server npm-audit
asked Jan 2 at 10:18
ma_dev_15ma_dev_15
409211
I have update the webpack-dev-server to the latest 3.1.14 but I am still getting vulnerability issue while using npm audit --fix. I have tries every thing. cleaning cache. clearing all modules and install again but all same.
Following is the error when I run npm audit
$ npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Missing Origin Validation
Package webpack-dev-server
Patched in >=3.1.11
Dependency of webpack-dev-server [dev]
Path webpack-dev-server
More info https://nodesecurity.io/advisories/725
found 1 high severity vulnerability in 60688 scanned packages
1 vulnerability requires manual review. See the full report for details.
security webpack-dev-server npm-audit
security webpack-dev-server npm-audit
asked Jan 2 at 10:18
ma_dev_15ma_dev_15
409211
asked Jan 2 at 10:18
ma_dev_15ma_dev_15
409211
edited Jan 2 at 11:15
ma_dev_15
asked Jan 2 at 10:18
ma_dev_15ma_dev_15
409211
asked Jan 2 at 10:18
ma_dev_15ma_dev_15
409211
asked Jan 2 at 10:18
ma_dev_15ma_dev_15
409211
409211
It is fixed by npm now.. RESOLVED
– ma_dev_15
Jan 3 at 3:39
add a comment |
It is fixed by npm now.. RESOLVED
– ma_dev_15
Jan 3 at 3:39
It is fixed by npm now.. RESOLVED
– ma_dev_15
Jan 3 at 3:39
It is fixed by npm now.. RESOLVED
– ma_dev_15
Jan 3 at 3:39
add a comment |
1 Answer
1
active
oldest
votes
Seems to be due to a typo in the npm vulnerability database. Hopefully fixed soon:
https://npm.community/t/npm-audit-sweems-to-get-semver-wrong/4352
answered Jan 2 at 13:11
HamundHamund
516714
1
Yes it is fixed by them now
– ma_dev_15
Jan 3 at 3:41
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54004545%2fwebpack-dev-server3-1-14-getting-missing-origin-validation-while-using-npm-audi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Seems to be due to a typo in the npm vulnerability database. Hopefully fixed soon:
https://npm.community/t/npm-audit-sweems-to-get-semver-wrong/4352
answered Jan 2 at 13:11
HamundHamund
516714
1
Yes it is fixed by them now
– ma_dev_15
Jan 3 at 3:41
add a comment |
Seems to be due to a typo in the npm vulnerability database. Hopefully fixed soon:
https://npm.community/t/npm-audit-sweems-to-get-semver-wrong/4352
answered Jan 2 at 13:11
HamundHamund
516714
1
Yes it is fixed by them now
– ma_dev_15
Jan 3 at 3:41
add a comment |
Seems to be due to a typo in the npm vulnerability database. Hopefully fixed soon:
https://npm.community/t/npm-audit-sweems-to-get-semver-wrong/4352
answered Jan 2 at 13:11
HamundHamund
516714
Seems to be due to a typo in the npm vulnerability database. Hopefully fixed soon:
https://npm.community/t/npm-audit-sweems-to-get-semver-wrong/4352
answered Jan 2 at 13:11
HamundHamund
516714
answered Jan 2 at 13:11
HamundHamund
516714
answered Jan 2 at 13:11
HamundHamund
516714
answered Jan 2 at 13:11
HamundHamund
516714
516714
1
Yes it is fixed by them now
– ma_dev_15
Jan 3 at 3:41
add a comment |
1
Yes it is fixed by them now
– ma_dev_15
Jan 3 at 3:41
1
1
Yes it is fixed by them now
– ma_dev_15
Jan 3 at 3:41
Yes it is fixed by them now
– ma_dev_15
Jan 3 at 3:41
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54004545%2fwebpack-dev-server3-1-14-getting-missing-origin-validation-while-using-npm-audi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It is fixed by npm now.. RESOLVED
– ma_dev_15
Jan 3 at 3:39