# CVE-2020-12079: Code injection in n/a

> Attackers can execute arbitrary code via sandbox escape in Beaker browser due to missing Electron context isolation and prototype pollution.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qxvv-6mm7-75fh

## What is CVE-2020-12079?

CVE-2020-12079 is a critical code injection vulnerability in n/a, published on 23 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Beaker before 0.8.9 allows a sandbox escape, enabling system access and code execution. This occurs because Electron context isolation is not used, and therefore an attacker can conduct a prototype-pollution attack against the Electron internal messaging API.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2020-12079?

It affects 1 product.


Products: Beakerbrowser Beaker.

## How do I fix CVE-2020-12079?

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

## Is CVE-2020-12079 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-7489](https://insights.sbomify.com/CVE-2013-7489/): Deserialization of Untrusted Data in Beaker (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12079 and fix it if it is affected.

What it is: CVE-2020-12079 is a critical code injection vulnerability in n/a, published on 23 Apr 2020. 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-2020-12079 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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