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

> Attackers can execute arbitrary code by tricking users into decompiling malicious .NET assemblies with embedded resources in Redgate tools.

- **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:** 31 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-43jr-65gg-fq95

## What is CVE-2018-14581?

CVE-2018-14581 is a high-severity code injection vulnerability in n/a, published on 31 Jul 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

Redgate .NET Reflector before 10.0.7.774 and SmartAssembly before 6.12.5 allow attackers to execute code by decompiling a compiled .NET object (such as a DLL or EXE file) with a specific embedded resource file.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Red-Gate .Net Reflector, Red-Gate Smartassembly.

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

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

## Is CVE-2018-14581 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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