How severe is GHSA-3gpc-w23c-w59w?

No CVSS score has been assigned to GHSA-3gpc-w23c-w59w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3gpc-w23c-w59w?

GHSA-3gpc-w23c-w59w affects the following packages: pitboss-ng (npm). Ecosystems affected: npm.

How do I fix GHSA-3gpc-w23c-w59w?

Update pitboss-ng to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3gpc-w23c-w59w is resolved across your whole dependency graph.

How do I detect GHSA-3gpc-w23c-w59w in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pitboss-ng, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3gpc-w23c-w59w if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-3gpc-w23c-w59w actively exploited in the wild?

No public exploit code has been indexed for GHSA-3gpc-w23c-w59w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-3gpc-w23c-w59w published, and has it been updated?

GHSA-3gpc-w23c-w59w was published on September 4, 2020 and was last updated on April 21, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Sandbox Breakout / Arbitrary Code Execution in pitboss-ngGHSA-3gpc-w23c-w59w

GHSA-3gpc-w23c-w59w is a remote code execution vulnerability in pitboss-ng. A fix is available for pitboss-ng — see the affected versions and patch details below.

Published

Sep 4, 2020

Updated

Apr 21, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 21, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

6other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

pitboss-ngnpm

2Kdownloads / week

Description

All versions of pitboss-ng 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`pitboss-ng`	all versions	2.0.0`npm install pitboss-ng@2.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pitboss-ng, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pitboss-ng to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3gpc-w23c-w59w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

All versions of `pitboss-ng` 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.

O3 Security · Impact-Aware SCA

Is GHSA-3gpc-w23c-w59w in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works