d3.js vulnerabilities and fixes

Recent CVEs affecting d3.js, with upgrade or downgrade steps. 1 tracked.

Also searched as: d3 js, d3js.

d3.js has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-06-04. Highest priority: CVE-2017-16044 (score 50/100).

• CVE-2017-16044 HIGH 7.5 MITIGATE `d3.js` was a malicious module published with the intent to hijack environment variables

FAQ

How do I fix d3.js vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is d3.js being exploited right now?

None of the tracked d3.js CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which d3.js CVE should I patch first?

CVE-2017-16044 currently ranks highest (50/100): `d3.js` was a malicious module published with the intent to hijack environment variables.

← Back to latest CVEs