Vulnerabilities in pkg:npm/wepack-cli
PACKAGEGHSA-fpw3-x4xq-6vxq is a CRITICAL (CVSS 9.8) malicious package vulnerability (CWE-506: Embedded Malicious Code) affecting Wepack cli libraries in the npm ecosystem. The issue involves malicious package in wepack-cli. Remediation is available in the latest vendor maintenance releases.
pkg:npm/wepack-cli
Vulnerability advisories affecting package pkg:npm/wepack-cli. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-fpw3-x4xq-6vxq | - | CRITICAL | Malicious Package in wepack-cli |
GHSA-fpw3-x4xq-6vxq at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix GHSA-fpw3-x4xq-6vxq
To remediate this vulnerability, upgrade all affected Wepack cli dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install wepack-cli@Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls wepack-cli
How to Check if You Are Affected
To determine whether your Node.js application is affected by GHSA-fpw3-x4xq-6vxq, inspect your project dependencies using npm:
npm ls wepack-cli
Analyze the terminal output to locate any version of Wepack cli in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The npm ls wepack-cli command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-506: Embedded Malicious Code, where the product contains code that appears to be malicious in nature. In Wepack cli, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-fpw3-x4xq-6vxq Affected Wepack cli Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
wepack-cli
|
npm |
|
|
References
Frequently Asked Questions
What is GHSA-fpw3-x4xq-6vxq?
Which Wepack cli versions are affected?
What version fixes GHSA-fpw3-x4xq-6vxq?
Is wepack-cli affected?
What is the CVSS score of GHSA-fpw3-x4xq-6vxq?
What CWE is associated with GHSA-fpw3-x4xq-6vxq?
How can I check npm dependencies for GHSA-fpw3-x4xq-6vxq?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-fpw3-x4xq-6vxq",
"modified" : "2021-10-01T13:46:23Z",
"published" : "2020-09-02T18:32:13Z",
"aliases" : [ ],
"summary" : "Malicious Package in wepack-cli",
"details" : "All versions of `wepack-cli` typosquatted a popular package of similar name and tracked users who had installed the incorrect package. The package uploaded information to a remote server including: name of the downloaded package, name of the intended package, the Node version and whether the process was running as sudo. There is no further compromise.\n\n\n## Recommendation\n\nRemove the package from your dependencies and always ensure package names are typed correctly upon installation.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "wepack-cli"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://www.npmjs.com/advisories/839"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-506" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2020-08-31T18:37:41Z",
"nvd_published_at" : null
}
}