# CVE-2020-26155: Privilege escalation in n/a

> Authenticated users can exploit weak file permissions and PATH entries to perform DLL hijacking, leading to privilege escalation and code execution.

- **Severity:** High 7.8 (`CVSS:3.1/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:** 18 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-65xq-8rp7-x2x4

## What is CVE-2020-26155?

CVE-2020-26155 is a high-severity vulnerability in n/a, published on 18 Mar 2021. 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

Multiple files and folders in Utimaco SecurityServer 4.20.0.4 and 4.31.1.0. are installed with Read/Write permissions for authenticated users, which allows for binaries to be manipulated by non-administrator users. Additionally, entries are made to the PATH environment variable which, in conjunction with these weak permissions, could enable an attacker to perform a DLL hijacking attack.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2020-26155?

It affects 6 products.


Products: Utimaco Block-Safe Firmware, Utimaco Cryptoserver Cp5 Firmware, Utimaco Cryptoserver Cp5 Vs-Nfd Firmware, Utimaco Paymentserver Firmware, Utimaco Paymentserver Hybrid Firmware, Utimaco Securityserver Firmware.

## How do I fix CVE-2020-26155?

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

## Is CVE-2020-26155 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26155 and fix it if it is affected.

What it is: CVE-2020-26155 is a high-severity vulnerability in n/a, published on 18 Mar 2021. 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-2020-26155 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-2020-26155/ (Markdown: https://insights.sbomify.com/CVE-2020-26155/index.md)
```

## Sources

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

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