Vulnerabilities in pkg:npm/veval

PACKAGE
Share
Advisory Summary

GHSA-54qm-37qr-w5wq is a CRITICAL sandbox breakout / arbitrary code vulnerability (General Security Weakness) affecting Veval libraries in the npm ecosystem. The issue involves sandbox breakout / arbitrary code execution in veval. Remediation is available in the latest vendor maintenance releases.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/veval

1 Known Advisory Record(s)

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

Advisory ID CVE / NVD Severity Summary
GHSA-54qm-37qr-w5wq - CRITICAL Sandbox Breakout / Arbitrary Code Execution in veval

GHSA-54qm-37qr-w5wq at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-54qm-37qr-w5wq
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Veval
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-54qm-37qr-w5wq

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

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

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-54qm-37qr-w5wq, inspect your project dependencies using npm:

npm ls veval

Analyze the terminal output to locate any version of Veval 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 veval 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 General Security Weakness. In Veval, 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 `veval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

GHSA-54qm-37qr-w5wq Affected Veval Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
veval
npm/veval
npm
≥ 0.0.0

References

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

Frequently Asked Questions

What is GHSA-54qm-37qr-w5wq?
GHSA-54qm-37qr-w5wq is a security vulnerability in Veval involving Sandbox Breakout / Arbitrary Code Execution in veval under General Security Weakness.
Which Veval versions are affected?
Affected versions include releases prior to current release patches across affected packages: veval.
What version fixes GHSA-54qm-37qr-w5wq?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is veval affected?
Yes, veval is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-54qm-37qr-w5wq?
GHSA-54qm-37qr-w5wq is classified under General Security Weakness.
How can I check npm dependencies for GHSA-54qm-37qr-w5wq?
Run the dependency tree command: 'npm ls veval'. 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-54qm-37qr-w5wq",
  "modified" : "2020-08-31T18:55:05Z",
  "published" : "2020-09-04T15:04:20Z",
  "aliases" : [ ],
  "summary" : "Sandbox Breakout / Arbitrary Code Execution in veval",
  "details" : "All versions of `veval` are vulnerable to Sandbox Escape leading to Remote Code Execution. The package fails to restrict access to the main context through `this.constructor.constructor` . This may allow attackers to execute arbitrary code in the system. Evaluating the payload `this.constructor.constructor('return process.env')()` prints the contents of `process.env`.\n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "veval"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/1321"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-08-31T18:55:05Z",
    "nvd_published_at" : null
  }
}