Vulnerabilities in pkg:npm/aysnc

PACKAGE
Advisory Summary

GHSA-gfjr-xqhm-qvv3 is a CRITICAL (CVSS 9.8) malicious package vulnerability (CWE-506: Embedded Malicious Code) affecting Aysnc libraries in the npm ecosystem. The issue involves malicious package in aysnc. Remediation is available in the latest vendor maintenance releases.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/aysnc

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/aysnc. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-gfjr-xqhm-qvv3 - CRITICAL Malicious Package in aysnc

GHSA-gfjr-xqhm-qvv3 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-gfjr-xqhm-qvv3
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Aysnc
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-gfjr-xqhm-qvv3

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

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

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-gfjr-xqhm-qvv3, inspect your project dependencies using npm:

npm ls aysnc

Analyze the terminal output to locate any version of Aysnc 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 aysnc 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 Aysnc, 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 `aysnc` 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-gfjr-xqhm-qvv3 Affected Aysnc Versions

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

References

Frequently Asked Questions

What is GHSA-gfjr-xqhm-qvv3?
GHSA-gfjr-xqhm-qvv3 is a security vulnerability in Aysnc involving Malicious Package in aysnc under CWE-506: Embedded Malicious Code.
Which Aysnc versions are affected?
Affected versions include releases prior to current release patches across affected packages: aysnc.
What version fixes GHSA-gfjr-xqhm-qvv3?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is aysnc affected?
Yes, aysnc 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-gfjr-xqhm-qvv3?
GHSA-gfjr-xqhm-qvv3 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-gfjr-xqhm-qvv3?
GHSA-gfjr-xqhm-qvv3 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-gfjr-xqhm-qvv3?
Run the dependency tree command: 'npm ls aysnc'. 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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-gfjr-xqhm-qvv3",
  "modified" : "2021-10-01T14:01:11Z",
  "published" : "2020-09-02T20:16:09Z",
  "aliases" : [ ],
  "summary" : "Malicious Package in aysnc",
  "details" : "All versions of `aysnc` 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" : "aysnc"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/848"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-08-31T18:38:02Z",
    "nvd_published_at" : null
  }
}