GHSA-5fm9-jmv7-fcx5: Asynnc Malicious Package Vulnerability

CRITICAL
Share
CVSS 9.8
CWE-506
Published
Advisory Summary

GHSA-5fm9-jmv7-fcx5 is a CRITICAL (CVSS 9.8) malicious package vulnerability (CWE-506: Embedded Malicious Code) affecting Asynnc libraries in the npm ecosystem. The issue involves malicious package in asynnc. Remediation is available in the latest vendor maintenance releases.

GHSA-5fm9-jmv7-fcx5 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-5fm9-jmv7-fcx5
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Asynnc
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-5fm9-jmv7-fcx5

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

asynnc fixed: Latest secure release 
npm install asynnc@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 asynnc

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-5fm9-jmv7-fcx5, inspect your project dependencies using npm:

npm ls asynnc

Analyze the terminal output to locate any version of Asynnc 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 asynnc 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 Asynnc, 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 `asynnc` 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-5fm9-jmv7-fcx5 Affected Asynnc Versions

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

References

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

Frequently Asked Questions

What is GHSA-5fm9-jmv7-fcx5?
GHSA-5fm9-jmv7-fcx5 is a security vulnerability in Asynnc involving Malicious Package in asynnc under CWE-506: Embedded Malicious Code.
Which Asynnc versions are affected?
Affected versions include releases prior to current release patches across affected packages: asynnc.
What version fixes GHSA-5fm9-jmv7-fcx5?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is asynnc affected?
Yes, asynnc 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-5fm9-jmv7-fcx5?
GHSA-5fm9-jmv7-fcx5 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-5fm9-jmv7-fcx5?
GHSA-5fm9-jmv7-fcx5 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-5fm9-jmv7-fcx5?
Run the dependency tree command: 'npm ls asynnc'. 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-5fm9-jmv7-fcx5",
  "modified" : "2021-10-01T13:47:05Z",
  "published" : "2020-09-02T18:35:26Z",
  "aliases" : [ ],
  "summary" : "Malicious Package in asynnc",
  "details" : "All versions of `asynnc` 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" : "asynnc"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/842"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-08-31T18:37:48Z",
    "nvd_published_at" : null
  }
}