# CVE-2019-19470: Deserialization in n/a

> Local attackers can escalate privileges to SYSTEM via unsafe .NET deserialization in TinyWall's named pipe processing.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fx9h-h562-86qx

## What is CVE-2019-19470?

CVE-2019-19470 is a high-severity unsafe deserialization vulnerability in n/a, published on 30 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unsafe usage of .NET deserialization in Named Pipe message processing allows privilege escalation to NT AUTHORITY\SYSTEM for a local attacker. Affected product is TinyWall, all versions up to and including 2.1.12. Fixed in version 2.1.13.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2019-19470?

It affects 1 product.


Products: Tinywall Tinywall.

## How do I fix CVE-2019-19470?

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

## Is CVE-2019-19470 being exploited?

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

Public exploit code:

- Este repositorio contiene el código y las instrucciones para replicar el exploit CVE-2019-19470 descubierto por CODEWHITE. Aquí se encuentran el código fuente de los ejemplos que utilicé en el meetup de HackTheBox para explicar mi proceso de aprendizaje y creación de este exploit.  (github_poc): https://github.com/juliourena/CVE-2019-19470-RedTeamRD

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19470 and fix it if it is affected.

What it is: CVE-2019-19470 is a high-severity unsafe deserialization vulnerability in n/a, published on 30 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19470 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-2019-19470/ (Markdown: https://insights.sbomify.com/CVE-2019-19470/index.md)
```

## Sources

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

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