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

> Local attackers can escalate privileges to admin by placing a malicious DLL in a temp folder before an admin runs the F-Secure installer.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-chc5-6p8h-wc5r

## What is CVE-2019-11644?

CVE-2019-11644 is a high-severity vulnerability in n/a, published on 17 May 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In the F-Secure installer in F-Secure SAFE for Windows before 17.6, F-Secure Internet Security before 17.6, F-Secure Anti-Virus before 17.6, F-Secure Client Security Standard and Premium before 14.10, F-Secure PSB Workstation Security before 12.01, and F-Secure Computer Protection Standard and Premium before 19.3, a local user can escalate their privileges through a DLL hijacking attack against the installer. The installer writes the file rm.exe to C:\Windows\Temp and then executes it. The rm.exe process then attempts to load several DLLs from its current directory. Non-admin users are able to write to this folder, so an attacker can create a malicious C:\Windows\Temp\OLEACC.dll file. When an admin runs the installer, rm.exe will execute the attacker's DLL in an elevated security context.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 5 products.


Products: F-Secure Client Security, F-Secure Computer Protection, F-Secure Internet Security, F-Secure Psb Workstation Security, F-Secure Safe.

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

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

## Is CVE-2019-11644 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-44750](https://insights.sbomify.com/CVE-2021-44750/): Arbitrary Code Execution (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11644 is a high-severity vulnerability in n/a, published on 17 May 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-11644 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-11644/ (Markdown: https://insights.sbomify.com/CVE-2019-11644/index.md)
```

## Sources

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

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