Sandbox Breakout / Arbitrary Code Execution in pitboss-ng

pitboss-ng Updated 02 Oct 2025

Summary

04/09/2020
CRITICAL
Yes i
Critical
Not published

GHSA-3gpc-w23c-w59w: Sandbox Breakout / Arbitrary Code Execution in pitboss-ng. Affects pitboss-ng versions < 2.0.0. Fixed in 2.0.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

pitboss-ng is an npm package that is used for sandboxing JavaScript code execution. It provides a secure environment for running untrusted code by restricting access to certain resources. However, all versions of pitboss-ng are vulnerable to a Sandbox Escape vulnerability, which can lead to Remote Code Execution. This vulnerability allows attackers to bypass the sandbox and execute arbitrary code in the system. The package fails to restrict access to the main context through this.constructor.constructor, which can be exploited by attackers.

Vulnerability Detail

The Sandbox Escape vulnerability in pitboss-ng arises from the package's inability to properly restrict access to the main context. By leveraging this.constructor.constructor, an attacker can execute arbitrary code in the system. For example, evaluating the payload this.constructor.constructor('return process.env')() allows an attacker to print the contents of process.env. This vulnerability poses a significant risk as it enables unauthorized code execution and potential system compromise.

How To Fix

Minimum fixed version

2.0.0

This is the first release that contains the fix.

npm install pitboss-ng@2.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As there is no fix available, a possible workaround is to manually review and modify the code of pitboss-ng to address the vulnerability. This may involve implementing proper access restrictions to the main context and ensuring that the sandbox environment is secure. However, this workaround requires a deep understanding of the package's code and may not be feasible for all users.

Conclusion

The Sandbox Breakout vulnerability in pitboss-ng exposes a critical security flaw that allows attackers to escape the sandbox and execute arbitrary code in the system. As there is currently no fix available, it is recommended to use an alternative package until a patch is released. Developers should stay updated with the official repository for any updates or patches addressing this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for pitboss-ng →

Share this vulnerability

FAQ

pitboss-ng is an npm package used for sandboxing JavaScript code execution. It provides a secure environment for running untrusted code.

The vulnerability allows attackers to escape the sandbox and execute arbitrary code in the system, potentially leading to unauthorized access, data breaches, or system compromise.

No, currently there is no fix available for this vulnerability in pitboss-ng. It is recommended to use an alternative package until a fix is released.

While there is no official fix, developers can manually review and modify the code of pitboss-ng to address the vulnerability. However, this requires a deep understanding of the package's code and may not be feasible for all users.

How To Fix

Minimum fixed version

2.0.0

This is the first release that contains the fix.

npm install pitboss-ng@2.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback