Cross-Site Scripting in c3

published 2020-09-01 6y ago modified 2023-11-08 3y ago also GHSA-gvg7-pp82-cff3

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

Affected versions of `c3` are vulnerable to cross-site scripting via improper sanitization of HTML in rendered tooltips.

## Recommendation

Update to 0.4.11 or later.

Patch / fix

fixed in 1 links 2

npm c3 0.4.11

github.com/c3js/c3@de38646 commit
github.com/c3js/c3#1675 pull request

Is CVE-2016-1000240 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
npm	c3	<0.4.11	0.4.11

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

github.com /c3js/c3/pull/1675
web
github.com /c3js/c3/commit/de3864650300488a63d0541620e9828b00e94b42
web
nvd.nist.gov /vuln/detail/CVE-2016-1000240
advisory
github.com /c3js/c3/issues/1536
web
github.com /c3js/c3
package
npmjs.com /advisories/138
web

Sources

GitHub Advisory GHSA-gvg7-pp82-cff3

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.