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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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.

How does O3 Security protect against GHSA-3gpc-w23c-w59w?

O3 pinpoints whether GHSA-3gpc-w23c-w59w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-3gpc-w23c-w59w

GHSA-3gpc-w23c-w59w is a remote code execution vulnerability in pitboss-ng. O3 Security confirms whether GHSA-3gpc-w23c-w59w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Sandbox Breakout / Arbitrary Code Execution in pitboss-ng

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

📦pitboss-ng

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether GHSA-3gpc-w23c-w59w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3gpc-w23c-w59w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-3gpc-w23c-w59w across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works