GHSA-h26f-j4mv-84g7: Asycn Malicious Package Vulnerability

CRITICAL
Share
CVSS 9.8
CWE-506
Published
Advisory Summary

GHSA-h26f-j4mv-84g7 is a CRITICAL (CVSS 9.8) malicious package vulnerability (CWE-506: Embedded Malicious Code) affecting Asycn libraries in the npm ecosystem. The issue involves malicious package in asycn. Remediation is available in the latest vendor maintenance releases.

GHSA-h26f-j4mv-84g7 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-h26f-j4mv-84g7
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Asycn
Package Ecosystem npm
Published Date
Last Updated

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).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-h26f-j4mv-84g7

To remediate this vulnerability, upgrade all affected Asycn dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

asycn fixed: Latest secure release 
npm install asycn@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls asycn

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-h26f-j4mv-84g7, inspect your project dependencies using npm:

npm ls asycn

Analyze the terminal output to locate any version of Asycn 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 asycn 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 Asycn, 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

All versions of `asycn` 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. ## Recommendation Remove the package from your dependencies and always ensure package names are typed correctly upon installation.

GHSA-h26f-j4mv-84g7 Affected Asycn Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
asycn
npm/asycn
npm

References

www.npmjs.com/advisories/846 WEB
https://www.npmjs.com/advisories/846

Frequently Asked Questions

What is GHSA-h26f-j4mv-84g7?
GHSA-h26f-j4mv-84g7 is a security vulnerability in Asycn involving Malicious Package in asycn under CWE-506: Embedded Malicious Code.
Which Asycn versions are affected?
Affected versions include releases prior to current release patches across affected packages: asycn.
What version fixes GHSA-h26f-j4mv-84g7?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is asycn affected?
Yes, asycn is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of GHSA-h26f-j4mv-84g7?
GHSA-h26f-j4mv-84g7 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with GHSA-h26f-j4mv-84g7?
GHSA-h26f-j4mv-84g7 is classified under CWE-506: Embedded Malicious Code (The product contains code that appears to be malicious in nature.).
How can I check npm dependencies for GHSA-h26f-j4mv-84g7?
Run the dependency tree command: 'npm ls asycn'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-h26f-j4mv-84g7",
  "modified" : "2021-10-01T14:00:36Z",
  "published" : "2020-09-02T18:39:43Z",
  "aliases" : [ ],
  "summary" : "Malicious Package in asycn",
  "details" : "All versions of `asycn` 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" : "asycn"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/846"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-08-31T18:37:57Z",
    "nvd_published_at" : null
  }
}