CVE-2016-5299

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A previously installed malicious Android application with same signature-level permissions as Firefox can intercept AuthTokens meant for Firefox only. Note: This issue only affects Firefox for Android. Other versions and operating systems are unaffected. This vulnerability affects Firefox < 50.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
73.6%
KEV
Not listed

Published

June 11, 2018

Last Modified

November 21, 2024

Frequently asked(5)

What is CVE-2016-5299?
CVE-2016-5299 is a high vulnerability published on June 11, 2018. A previously installed malicious Android application with same signature-level permissions as Firefox can intercept AuthTokens meant for Firefox only. Note: This issue only affects Firefox for Android. Other versions and operating systems are unaffected. This vulnerability affects Firefox < 50.
When was CVE-2016-5299 disclosed?
CVE-2016-5299 was first published in the National Vulnerability Database on June 11, 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-2016-5299 actively exploited?
CVE-2016-5299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 73.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-5299?
CVE-2016-5299 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2016-5299?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-5299, 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

Explore the affected products and dependency analysis for CVE-2016-5299

Explore →

Is Your Infrastructure Affected by CVE-2016-5299?

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