# CVE-2017-20051: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 16 Jun 2022
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-37pr-3jcm-ppm2

## What is CVE-2017-20051?

CVE-2017-20051 is a vulnerability, published on 16 Jun 2022. 

### Official description

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: The sole source documents PE-format conformance defects in innosetup-5.5.9.exe with no exploit, attack path, or untrusted search path condition (CWE-426/427), and the author states Windows loads these files normally; the record's remote/exploited claims are unsupported, as is the product maintainer's contention.

## Which versions are affected by CVE-2017-20051?


## How do I fix CVE-2017-20051?

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

## Is CVE-2017-20051 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20051 and fix it if it is affected.

What it is: CVE-2017-20051 is a vulnerability, published on 16 Jun 2022. 
Exploitation: There is no known exploitation of CVE-2017-20051 in the wild and no public exploit code.

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-2017-20051/ (Markdown: https://insights.sbomify.com/CVE-2017-20051/index.md)
```

## Sources

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

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