# CVE-2018-11544: Information disclosure in n/a

> An attacker with device access can read stored FTP credentials from insecure shared preferences, potentially leading to unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2018
- **Updated:** 11 Nov 2025
- **Also known as:** GHSA-v3mf-38wr-ph3h

## What is CVE-2018-11544?

CVE-2018-11544 is a critical vulnerability in n/a, published on 29 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Olive Tree Ftp Server application 1.32 for Android has Insecure Data Storage because a username and password are stored in the /data/data/com.theolivetree.ftpserver/shared_prefs/com.theolivetree.ftpserver_preferences.xml file as the prefUsername and prefUserpass strings.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2018-11544?

It affects 1 product.


Products: Theolivetree Ftp Server.

## How do I fix CVE-2018-11544?

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

## Is CVE-2018-11544 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9600](https://insights.sbomify.com/CVE-2019-9600/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11544 and fix it if it is affected.

What it is: CVE-2018-11544 is a critical vulnerability in n/a, published on 29 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11544 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-2018-11544/ (Markdown: https://insights.sbomify.com/CVE-2018-11544/index.md)
```

## Sources

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

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