# CVE-2019-6447: Missing authorization in n/a

> Remote attackers on the local Wi-Fi network can read arbitrary files or execute applications via unauthenticated HTTP requests to an open TCP port.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2pqf-jwpx-hmhw

## What is CVE-2019-6447?

CVE-2019-6447 is a high-severity missing authorization vulnerability in n/a, published on 16 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ES File Explorer File Manager application through 4.1.9.7.4 for Android allows remote attackers to read arbitrary files or execute applications via TCP port 59777 requests on the local Wi-Fi network. This TCP port remains open after the ES application has been launched once, and responds to unauthenticated application/json data over HTTP.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Estrongs Es File Explorer File Manager.

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

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

## Is CVE-2019-6447 being exploited?

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

Public exploit code:

- ES File Explorer Open Port Vulnerability - CVE-2019-6447 (github_poc): https://github.com/fs0c131y/ESFileExplorerOpenPortVuln
- Exploiting Android Vulnerability in ES File Explorer (github_poc): https://github.com/Chethine/EsFileExplorer-CVE-2019-6447
- ES File Explorer Open Port (metasploit)
- ES File Explorer Open Port Vulnerability - CVE-2019-6447 (github_poc): https://github.com/SandaRuFdo/ES-File-Explorer-Open-Port-Vulnerability---CVE-2019-6447
- ES File Explorer 4.1.9.7.4 - Arbitrary File Read (exploitdb)
- https://github.com/h3x0v3rl0rd/CVE-2019-6447 (github_poc): https://github.com/h3x0v3rl0rd/CVE-2019-6447

## Other vulnerabilities in n/a

- [CVE-2019-11380](https://insights.sbomify.com/CVE-2019-11380/): Auth bypass in n/a (high 7.5)
- [CVE-2019-8345](https://insights.sbomify.com/CVE-2019-8345/): Other in n/a (medium 4.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6447 is a high-severity missing authorization vulnerability in n/a, published on 16 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-6447 exists.

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

## Sources

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

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