# CVE-2019-16116: Information disclosure in n/a

> An attacker can read the Bootstrap.log file to obtain the administrator password hash, potentially leading to account takeover.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7r7h-68mg-gxrx

## What is CVE-2019-16116?

CVE-2019-16116 is a medium-severity vulnerability in n/a, published on 2 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EnterpriseDT CompleteFTP Server prior to version 12.1.3 is vulnerable to information exposure in the Bootstrap.log file. This allows an attacker to obtain the administrator password hash.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2019-16116?

It affects 1 product.


Products: Enterprisedt Completeftp Server.

## How do I fix CVE-2019-16116?

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

## Is CVE-2019-16116 being exploited?

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

Public exploit code:

- CompleteFTP Professional 12.1.3 - Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2019-16864](https://insights.sbomify.com/CVE-2019-16864/): Command injection in n/a (high 8.8)
- [CVE-2022-2560](https://insights.sbomify.com/CVE-2022-2560/): Path traversal in CompleteFTP (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16116 and fix it if it is affected.

What it is: CVE-2019-16116 is a medium-severity vulnerability in n/a, published on 2 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16116 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-2019-16116/ (Markdown: https://insights.sbomify.com/CVE-2019-16116/index.md)
```

## Sources

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

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