# CVE-2022-23923: Sandbox Bypass

> Attackers can bypass the jailed sandbox restrictions by accessing the main application via an exported alert method, potentially executing arbitrary code.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-77m7-9wvw-87fx

## What is CVE-2022-23923?

CVE-2022-23923 is a high-severity vulnerability in jailed, published on 1 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of package jailed are vulnerable to Sandbox Bypass via an exported alert() method which can access the main application. Exported methods are stored in the application.remote object.

## Which versions are affected by CVE-2022-23923?

2 open source packages ship an affected version, including jailed. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jailed` | npm | All versions to 0.3.1 | None |
| `jailed` | npm | All versions to 0.3.1 | None |

Products: Jailed Project Jailed.

## How do I fix CVE-2022-23923?

No fix has been published for CVE-2022-23923 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-23923 being exploited?

There is no known exploitation of CVE-2022-23923 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23923 and fix it if it is affected.

What it is: CVE-2022-23923 is a high-severity vulnerability in jailed, published on 1 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23923 in the wild and no public exploit code.

Affected packages and fixed versions:
- jailed (npm): affected all versions up to 0.3.1; no fix listed
- jailed (npm): affected all versions up to 0.3.1; no fix listed

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/CVE-2022-23923/ (Markdown: https://insights.sbomify.com/CVE-2022-23923/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23923
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23923
- OSV: https://osv.dev/vulnerability/CVE-2022-23923

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-23923/
Summaries are generated and may contain mistakes; the official description above is the record.