Vulnerabilities in pkg:npm/bufver-xor
PACKAGEGHSA-cr4x-w2v7-4mmf is a CRITICAL (CVSS 9.8) malicious package vulnerability (CWE-506: Embedded Malicious Code) affecting Bufver xor libraries in the npm ecosystem. The issue involves malicious package in bufver-xor. Remediation is available in the latest vendor maintenance releases.
pkg:npm/bufver-xor
Vulnerability advisories affecting package pkg:npm/bufver-xor. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-cr4x-w2v7-4mmf | - | CRITICAL | Malicious Package in bufver-xor |
GHSA-cr4x-w2v7-4mmf 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-cr4x-w2v7-4mmf
To remediate this vulnerability, upgrade all affected Bufver xor 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 bufver-xor@Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls bufver-xor
How to Check if You Are Affected
To determine whether your Node.js application is affected by GHSA-cr4x-w2v7-4mmf, inspect your project dependencies using npm:
npm ls bufver-xor
Analyze the terminal output to locate any version of Bufver xor 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 bufver-xor 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 Bufver xor, 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-cr4x-w2v7-4mmf Affected Bufver xor Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
bufver-xor
|
npm |
≥ 0.0.0
|
|
References
Frequently Asked Questions
What is GHSA-cr4x-w2v7-4mmf?
Which Bufver xor versions are affected?
What version fixes GHSA-cr4x-w2v7-4mmf?
Is bufver-xor affected?
What is the CVSS score of GHSA-cr4x-w2v7-4mmf?
What CWE is associated with GHSA-cr4x-w2v7-4mmf?
How can I check npm dependencies for GHSA-cr4x-w2v7-4mmf?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-cr4x-w2v7-4mmf",
"modified" : "2021-09-29T21:36:13Z",
"published" : "2020-09-03T22:26:13Z",
"aliases" : [ ],
"summary" : "Malicious Package in bufver-xor",
"details" : "Version 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.\n\n\n## Recommendation\n\nRemove the package from your environment. Ensure no Ethereum funds were compromised.",
"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" : "bufver-xor"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.0.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://www.npmjs.com/advisories/1265"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-506" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2020-08-31T18:53:00Z",
"nvd_published_at" : null
}
}