# CVE-2019-9486: Privilege escalation in n/a

> Local attackers can escalate privileges to SYSTEM by hijacking insecure named pipe communications in the HiDrive Maintenance Service.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2ghq-8m9c-mqjm

## What is CVE-2019-9486?

CVE-2019-9486 is a high-severity vulnerability in n/a, published on 30 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

STRATO HiDrive Desktop Client 5.0.1.0 for Windows suffers from a SYSTEM privilege escalation vulnerability through the HiDriveMaintenanceService service. This service establishes a NetNamedPipe endpoint that allows applications to connect and call publicly exposed methods. An attacker can inject and execute code by hijacking the insecure communications with the service. This vulnerability also affects Telekom MagentaCLOUD through 5.7.0.0 and 1&1 Online Storage through 6.1.0.0.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 3 products.


Products: Ionos 1\&1 Online Storage, Strato Hidrive Desktop Client, Telekom Magentacloud.

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

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

## Is CVE-2019-9486 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9486 is a high-severity vulnerability in n/a, published on 30 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9486 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-9486/ (Markdown: https://insights.sbomify.com/CVE-2019-9486/index.md)
```

## Sources

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

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