CVE-2019-13099: The Momo application 2.1.9 for Android stores confidential information insecurely on the system (i.e., in clea

This month

MEDIUM 6.5DOWNGRADE

CVE-2019-13099 is a medium-severity flaw (CVSS 6.5) affecting momo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Momo application 2.1.9 for Android stores confidential information insecurely on the system (i.e., in cleartext), which allows a non-root user to find out the username/password of a valid user and a user's access token via Logcat.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 45%)
CISA exploited list	No
Weakness	CWE-312
Published	2019-07-22
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: momo project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-07-22 16:15 UTCPublished CVE record published
2026-06-17 02:16 UTCUpdated Record last modified

momo project momo DOWNGRADE

Affected: 2.1.9

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.1.9

1. Check installed version

apt-cache policy momo || rpm -q momo || momo --version

2. No fixed release: DOWNGRADE to a release before 2.1.9 (Debian / Ubuntu)

apt-cache madison momo sudo apt install momo=<VERSION_BEFORE_2.1.9> sudo apt-mark hold momo

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list momo sudo dnf downgrade momo-<VERSION_BEFORE_2.1.9> sudo dnf versionlock add momo

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-13099?

momo: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-13099 being exploited?

CVE-2019-13099 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-13099 affect?

CVE-2019-13099 affects momo. Severity is medium (CVSS 6.5). The Momo application 2.1.9 for Android stores confidential information insecurely on the system (i.e., in cleartext), which allows a non-root user to find out the username/password of a valid user and a user's access token via Logcat.

How urgent is CVE-2019-13099?

Priority 42/100. Public exploit reference

Software pages

Android vulnerabilities

References

← Back to latest CVEs