# CVE-2018-16545: Code injection in n/a

> Remote attackers can achieve arbitrary code execution in Kaizen Asset Manager and Training Manager by impersonating temporary files with malicious DLLs or executables.

- **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:** 5 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2w6g-rjx6-85cp

## What is CVE-2018-16545?

CVE-2018-16545 is a high-severity code injection vulnerability in n/a, published on 5 Sep 2018. 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

Kaizen Asset Manager (Enterprise Edition) and Training Manager (Enterprise Edition) allow a remote attacker to achieve arbitrary code execution via file impersonation. For example, a malicious dynamic-link library (dll) assumed the identity of a temporary (tmp) file (isxdl.dll) and an executable file assumed the identity of a temporary file (996E.temp).

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-16545?

It affects 2 products.


Products: Kzsoftware Asset Manager, Kzsoftware Training Manager.

## How do I fix CVE-2018-16545?

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

## Is CVE-2018-16545 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16545 and fix it if it is affected.

What it is: CVE-2018-16545 is a high-severity code injection vulnerability in n/a, published on 5 Sep 2018. 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-2018-16545 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-2018-16545/ (Markdown: https://insights.sbomify.com/CVE-2018-16545/index.md)
```

## Sources

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

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