# CVE-2019-8345: Other in n/a

> Man-in-the-middle attackers can hijack sessions in ES File Explorer by intercepting unencrypted HTTP traffic and displaying malicious content in a WebView.

- **Severity:** Medium 4.2 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/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:** 15 Feb 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7gvm-32f4-3mv5

## What is CVE-2019-8345?

CVE-2019-8345 is a medium-severity vulnerability in n/a, published on 15 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Help feature in the ES File Explorer File Manager application 4.1.9.7.4 for Android allows session hijacking by a Man-in-the-middle attacker on the local network because HTTPS is not used, and an attacker's web site is displayed in a WebView with no information about the URL.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Estrongs Es File Explorer File Manager.

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

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

## Is CVE-2019-8345 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-6447](https://insights.sbomify.com/CVE-2019-6447/): Missing authorization in n/a (high 8.1)
- [CVE-2019-11380](https://insights.sbomify.com/CVE-2019-11380/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-8345 is a medium-severity vulnerability in n/a, published on 15 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-8345 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-8345/ (Markdown: https://insights.sbomify.com/CVE-2019-8345/index.md)
```

## Sources

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

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