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

> The Rediffmail Android application stores mail content in cleartext files that persist after logout, allowing local attackers to read sensitive emails.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 9 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-54fp-gh3m-g9m6

## What is CVE-2019-11836?

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

### Official description

The Rediffmail (aka com.rediff.mail.and) application 2.2.6 for Android has cleartext mail content in file storage, persisting after a logout.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Rediff Rediffmail.

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

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

## Is CVE-2019-11836 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11836 is a medium-severity vulnerability in n/a, published on 9 May 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-11836 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-11836/ (Markdown: https://insights.sbomify.com/CVE-2019-11836/index.md)
```

## Sources

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

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