CVE-2017-16905

HIGHNVD 8.18.1—

8.1

The DuoLingo TinyCards application before 1.0 for Android has one use of unencrypted HTTP, which allows remote attackers to spoof content, and consequently achieve remote code execution, via a man-in-the-middle attack.

CVSS v3: 8.1
EG Score: 8.1(medium)
EPSS: 85.8%
KEV: Not listed

Published

January 5, 2018

Last Modified

November 21, 2024

References (4)

cve@mitrehttps://hackerone.com/reports/281605
cve@mitrehttps://wwws.nightwatchcybersecurity.com/2018/01/04/rce-in-duolingos-tinycards-app-for-android-cve-2017-16905/
af854a3a-2127-422b-91ae-364da2661108https://hackerone.com/reports/281605
af854a3a-2127-422b-91ae-364da2661108https://wwws.nightwatchcybersecurity.com/2018/01/04/rce-in-duolingos-tinycards-app-for-android-cve-2017-16905/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-94Improper Control of Generation of Code (Code Injection)

Data Freshness Timeline

(refreshed 11× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 22:44 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2017-16905?

CVE-2017-16905 is a high vulnerability published on January 5, 2018. The DuoLingo TinyCards application before 1.0 for Android has one use of unencrypted HTTP, which allows remote attackers to spoof content, and consequently achieve remote code execution, via a man-in-the-middle attack.

When was CVE-2017-16905 disclosed?

CVE-2017-16905 was first published in the National Vulnerability Database on January 5, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-16905 actively exploited?

CVE-2017-16905 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2017-16905?

CVE-2017-16905 has a CVSS v3 base score of 8.1 (NVD).

How do I remediate CVE-2017-16905?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16905, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-16905

Explore →

Is Your Infrastructure Affected by CVE-2017-16905?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2017-16905

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2017-16905?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)