# CVE-2020-14449: Information disclosure in n/a

> Attackers can obtain authorization tokens from Mattermost Mobile Apps, potentially leading to account takeover and data exposure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-366p-28vc-x7xr

## What is CVE-2020-14449?

CVE-2020-14449 is a high-severity vulnerability in n/a, published on 19 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Mattermost Mobile Apps before 1.30.0. Authorization tokens can sometimes be disclosed to third-party servers, aka MMSA-2020-0018.

## Which versions are affected by CVE-2020-14449?

It affects 1 product.


Products: Mattermost Mattermost Mobile.

## How do I fix CVE-2020-14449?

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

## Is CVE-2020-14449 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20848](https://insights.sbomify.com/CVE-2019-20848/): Other in n/a (high 7.5)
- [CVE-2019-20852](https://insights.sbomify.com/CVE-2019-20852/): Information disclosure in n/a (high 7.5)
- [CVE-2020-14451](https://insights.sbomify.com/CVE-2020-14451/): Information disclosure in n/a (high 7.5)
- [CVE-2025-1558](https://insights.sbomify.com/CVE-2025-1558/): Denial of Service Via Malicious GIF (medium 6.5)
- [CVE-2025-20072](https://insights.sbomify.com/CVE-2025-20072/): Mobile crash via improper validation of proto style in attachments (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14449 and fix it if it is affected.

What it is: CVE-2020-14449 is a high-severity vulnerability in n/a, published on 19 Jun 2020. 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-2020-14449 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-2020-14449/ (Markdown: https://insights.sbomify.com/CVE-2020-14449/index.md)
```

## Sources

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

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