# CVE-2021-41392: Command injection in n/a

> Remote attackers can execute arbitrary commands on Boost Note desktop clients by sending crafted IPC messages to the exposed interface.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 17 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8h86-6q3w-5h6p

## What is CVE-2021-41392?

CVE-2021-41392 is a critical command injection vulnerability in n/a, published on 17 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

static/main-preload.js in Boost Note through 0.22.0 allows remote command execution. A remote attacker may send a crafted IPC message to the exposed vulnerable ipcRenderer IPC interface, which invokes the dangerous openExternal Electron API.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2021-41392?

It affects 1 product.


Products: Boostnote Boostnote.

## How do I fix CVE-2021-41392?

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

## Is CVE-2021-41392 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-13433](https://insights.sbomify.com/CVE-2018-13433/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41392 and fix it if it is affected.

What it is: CVE-2021-41392 is a critical command injection vulnerability in n/a, published on 17 Sep 2021. 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-2021-41392 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-2021-41392/ (Markdown: https://insights.sbomify.com/CVE-2021-41392/index.md)
```

## Sources

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

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