# CVE-2015-4107: DO NOT USE THIS CANDIDATE NUMBER.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Jan 2020
- **Updated:** 14 Jan 2020

## What is CVE-2015-4107?

CVE-2015-4107 is a vulnerability, published on 14 Jan 2020. 

### Official description

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was intended functionality. Notes: none

## Which versions are affected by CVE-2015-4107?


## How do I fix CVE-2015-4107?

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

## Is CVE-2015-4107 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-4107 exists.

Public exploit code:

- Wing FTP Server - (Authenticated) Command Execution (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4107 and fix it if it is affected.

What it is: CVE-2015-4107 is a vulnerability, published on 14 Jan 2020. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-4107 exists.

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

## Sources

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

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