# CVE-2022-21167: Arbitrary Code Execution

> Attackers can execute arbitrary code via unsafe BinaryFormatter deserialization in the SocketClient component of the Masuit.Tools.Core library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vh38-ghx6-vmvg

## What is CVE-2022-21167?

CVE-2022-21167 is a high-severity unsafe deserialization vulnerability in Masuit.Tools.Core, published on 1 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

All versions of package masuit.tools.core are vulnerable to Arbitrary Code Execution via the ReceiveVarData<T> function in the SocketClient.cs component. The socket client in the package can pass in the payload via the user-controllable input after it has been established, because this socket client transmission does not have the appropriate restrictions or type bindings for the BinaryFormatter.

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

2 open source packages ship an affected version, including Masuit.Tools.Core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Masuit.Tools.Core` | NuGet | All versions to 2.4.8.6 | None |
| `Masuit.Tools.Core` | NuGet | All versions to 2.4.8.6 | None |

Products: Ldqk Masuit.tools.

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

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

## Is CVE-2022-21167 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21167 is a high-severity unsafe deserialization vulnerability in Masuit.Tools.Core, published on 1 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-21167 in the wild and no public exploit code.

Affected packages and fixed versions:
- Masuit.Tools.Core (NuGet): affected all versions up to 2.4.8.6; no fix listed
- Masuit.Tools.Core (NuGet): affected all versions up to 2.4.8.6; 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-21167/ (Markdown: https://insights.sbomify.com/CVE-2022-21167/index.md)
```

## Sources

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

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