# CVE-2021-32647: Post-authentication Remote Code Execution (RCE) in emissary:emissary

> Post-authentication attackers can achieve remote code execution or denial of service by loading arbitrary classes via the CreatePlace endpoint.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-ph73-7v9r-wg32

## What is CVE-2021-32647?

CVE-2021-32647 is a high-severity code injection vulnerability in NationalSecurityAgency emissary, published on 28 May 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Emissary is a P2P based data-driven workflow engine. Affected versions of Emissary are vulnerable to post-authentication Remote Code Execution (RCE). The [`CreatePlace`](https://github.com/NationalSecurityAgency/emissary/blob/30c54ef16c6eb6ed09604a929939fb9f66868382/src/main/java/emissary/server/mvc/internal/CreatePlaceAction.java#L36) REST endpoint accepts an `sppClassName` parameter which is used to load an arbitrary class. This class is later instantiated using a constructor with the following signature: `<constructor>(String, String, String)`. An attacker may find a gadget (class) in the application classpath that could be used to achieve Remote Code Execution (RCE) or disrupt the application. Even though the chances to find a gadget (class) that allow arbitrary code execution are low, an attacker can still find gadgets that could potentially crash the application or leak sensitive data. As a work around disable network access to Emissary from untrusted sources.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Nsa Emissary.

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

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

## Is CVE-2021-32647 being exploited?

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

## Other vulnerabilities in NationalSecurityAgency emissary

- [CVE-2026-35580](https://insights.sbomify.com/CVE-2026-35580/): Emissary has GitHub Actions Shell Injection via Workflow Inputs (critical 9.1)
- [CVE-2026-35582](https://insights.sbomify.com/CVE-2026-35582/): Emissary has an OS Command Injection via Unvalidated IN_FILE_ENDING / OUT_FILE_ENDING in Executrix (high 8.8)
- [CVE-2021-32094](https://insights.sbomify.com/CVE-2021-32094/): File upload in n/a (high 8.8)
- [CVE-2021-32096](https://insights.sbomify.com/CVE-2021-32096/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2021-32095](https://insights.sbomify.com/CVE-2021-32095/): Missing authorization in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-32647 is a high-severity code injection vulnerability in NationalSecurityAgency emissary, published on 28 May 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-32647 in the wild and no public exploit code.

Affected product: NationalSecurityAgency emissary. 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-32647/ (Markdown: https://insights.sbomify.com/CVE-2021-32647/index.md)
```

## Sources

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

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