# CVE-2019-3980: File upload in SolarWinds Dameware Remote Mini Remote Client Agent Service

> An unauthenticated remote attacker can upload and execute arbitrary code with Local System privileges via the smart card authentication feature.

- **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:** 8 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9qx2-7jwx-q6pj

## What is CVE-2019-3980?

CVE-2019-3980 is a critical vulnerability in SolarWinds Dameware Remote Mini Remote Client Agent Service, published on 8 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Solarwinds Dameware Mini Remote Client agent v12.1.0.89 supports smart card authentication which can allow a user to upload an executable to be executed on the DWRCS.exe host. An unauthenticated, remote attacker can request smart card login and upload and execute an arbitrary executable run under the Local System account.

Weakness: CWE-346 (Origin Validation Error)

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

It affects 1 product.


Products: Solarwinds Dameware Mini Remote Control.

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

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

## Is CVE-2019-3980 being exploited?

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

Public exploit code:

- https://github.com/warferik/CVE-2019-3980 (github_poc): https://github.com/warferik/CVE-2019-3980
- Python 3 exploit for CVE-2019-3980. Unauthenticated RCE as SYSTEM via SolarWinds Dameware MRC smart card authentication bypass. (github_poc): https://github.com/boydhacks/dameflare
- CVE-2019-3980 exploit written in win32/c++ (openssl dependency). Port of https://github.com/tenable/poc/blob/master/Solarwinds/Dameware/dwrcs_dwDrvInst_rce.py (github_poc): https://github.com/Barbarisch/CVE-2019-3980
- https://github.com/CyberQuestor-infosec/CVE-2019-3980-Open_Net_Admin_v18.1.1_RCE (github_poc): https://github.com/CyberQuestor-infosec/CVE-2019-3980-Open_Net_Admin_v18.1.1_RCE

## Other vulnerabilities in SolarWinds Dameware Remote Mini Remote Client Agent Service

- [CVE-2021-31217](https://insights.sbomify.com/CVE-2021-31217/): Missing authorization in n/a (critical 9.1)
- [CVE-2018-12897](https://insights.sbomify.com/CVE-2018-12897/): Memory corruption in n/a (high 7.8)
- [CVE-2019-9017](https://insights.sbomify.com/CVE-2019-9017/): Memory corruption in n/a (high 7.5)
- [CVE-2015-8220](https://insights.sbomify.com/CVE-2015-8220/): Memory corruption in n/a (high 7.5)
- [CVE-2019-3957](https://insights.sbomify.com/CVE-2019-3957/): Information disclosure in Solarwinds Dameware Remote Mini Controller (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3980 is a critical vulnerability in SolarWinds Dameware Remote Mini Remote Client Agent Service, published on 8 Oct 2019. 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-2019-3980 in the wild and no public exploit code.

Affected product: SolarWinds Dameware Remote Mini Remote Client Agent Service. 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-3980/ (Markdown: https://insights.sbomify.com/CVE-2019-3980/index.md)
```

## Sources

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

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