# GHSA-4vmm-mhcq-4x9j: Sandbox Bypass Leading to Arbitrary Code Execution in constantinople

> An attacker can bypass the sandbox in the constantinople library to execute arbitrary code on the host system.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jun 2019

## What is GHSA-4vmm-mhcq-4x9j?

GHSA-4vmm-mhcq-4x9j is a code injection vulnerability in constantinople, published on 14 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `constantinople` prior to 3.1.1 are vulnerable to a sandbox bypass which can lead to arbitrary code execution.

## Recommendation

Update to version 3.1.1 or later.

## Which versions are affected by GHSA-4vmm-mhcq-4x9j?

2 open source packages ship an affected version, including constantinople.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `constantinople` | npm | All versions | 3.1.1 |
| `constantinople` | npm | All versions | 3.1.1 |

## How do I fix GHSA-4vmm-mhcq-4x9j?

Upgrade constantinople to 3.1.1 or later.

## Is GHSA-4vmm-mhcq-4x9j being exploited?

There is no known exploitation of GHSA-4vmm-mhcq-4x9j in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4vmm-mhcq-4x9j and fix it if it is affected.

What it is: GHSA-4vmm-mhcq-4x9j is a code injection vulnerability in constantinople, published on 14 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-4vmm-mhcq-4x9j in the wild and no public exploit code.

Affected packages and fixed versions:
- constantinople (npm): affected all versions; fixed in 3.1.1
- constantinople (npm): affected all versions; fixed in 3.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-4vmm-mhcq-4x9j/ (Markdown: https://insights.sbomify.com/GHSA-4vmm-mhcq-4x9j/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4vmm-mhcq-4x9j

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4vmm-mhcq-4x9j/
Summaries are generated and may contain mistakes; the official description above is the record.