CVE-2019-18841 json
Prototype Pollution in chartkick
published 6y ago modified 4mo ago also GHSA-5pm8-492c-92p5 , EUVD-2019-0780
- cvss
- 7.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
Chartkick.js 3.1.0 through 3.1.3, as used in the Chartkick gem before 3.3.0 for Ruby, allows prototype pollution.
Patch / fix
- rubygems chartkick 3.3.0
- npm chartkick 3.2.0
Is CVE-2019-18841 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 FencerExploit prediction
1.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | chartkick | <3.3.0 |
3.3.0 |
| npm | chartkick | >=3.1.0, <3.2.0 |
3.2.0 |
References
-
github.com
/ankane/chartkick/commit/b810936bbf687bc74c5b6dba72d2397a399885fa
web, patch
-
github.com
/ankane/chartkick/commits/master
web, patch
-
rubygems.org
/gems/chartkick/
product, release-notes
-
chartkick.com
web, product
-
github.com
/ankane/chartkick/blob/master/CHANGELOG.md
web, product, release-notes
-
github.com
/ankane/chartkick.js/issues/117
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-18841
advisory
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/chartkick/CVE-2019-18841.yml
web
-
rubygems.org
/gems/chartkick
web
Sources
- CVE List CVE-2019-18841
- GitHub Advisory GHSA-5pm8-492c-92p5
- NVD CVE-2019-18841
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.