# CVE-2017-18774: DO NOT USE THIS CANDIDATE NUMBER.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 May 2020
- **Updated:** 5 May 2020
- **Also known as:** GHSA-62vh-cjp3-26j8

## What is CVE-2017-18774?

CVE-2017-18774 is a vulnerability, published on 4 May 2020. 

### Official description

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2018-21139, CVE-2017-18867. Reason: this candidate was intended for one issue, but the description and references inadvertently combined multiple issues. Notes: All CVE users should consult CVE-2018-21139 and CVE-2017-18867 to determine which ID is appropriate. All references and descriptions in this candidate have been removed to prevent accidental usage

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


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

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

## Is CVE-2017-18774 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18774 is a vulnerability, published on 4 May 2020. 
Exploitation: There is no known exploitation of CVE-2017-18774 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-18774/ (Markdown: https://insights.sbomify.com/CVE-2017-18774/index.md)
```

## Sources

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

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