dalek-browser-chrome-canary provides Google Chrome bindings for DalekJS. dalek-browser-chrome-canary downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.
CVE-2016-10584
HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 33% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 8.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EPSS
- 79.1%
- KEV
- Not listed
Published
May 29, 2018
Last Modified
November 21, 2024
References (2)
- support@hackeronehttps://nodesecurity.io/advisories/181
- af854a3a-2127-422b-91ae-364da2661108https://nodesecurity.io/advisories/181
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| dalek-browser-chrome-canary | — | — | — |
Frequently asked(5)
What is CVE-2016-10584?
CVE-2016-10584 is a high vulnerability published on May 29, 2018. dalek-browser-chrome-canary provides Google Chrome bindings for DalekJS. dalek-browser-chrome-canary downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested binary with an attacker…
When was CVE-2016-10584 disclosed?
CVE-2016-10584 was first published in the National Vulnerability Database on May 29, 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-10584 actively exploited?
CVE-2016-10584 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 79.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-10584?
CVE-2016-10584 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2016-10584?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-10584, 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-2016-10584
Is Your Infrastructure Affected by CVE-2016-10584?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.