chartkick vulnerabilities
Create beautiful JavaScript charts with one line of Ruby
- Registry
- RubyGems
- Latest
- 5.3.0
- License
- MIT
3 known advisories
The latest version, 5.3.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
bundle update --conservative chartkick # Gemfile: '>= 5.3.0'Is your project on an affected chartkick?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for chartkick
CSS Injection in Chartkick gem
- Affected
- <3.4.0
- Fixed in
- 3.4.0
Prototype Pollution in chartkick
- Affected
- <3.3.0
- Fixed in
- 3.3.0
Cross-site Scripting in Chartkick
- Affected
- <3.2.0
- Fixed in
- 3.2.0
Is your chartkick version vulnerable?
- chartkick 5.3No known advisories in 5.3.0
- chartkick 5.2No known advisories in 5.2.1
- chartkick 5.1No known advisories in 5.1.5
- chartkick 5.0No known advisories in 5.0.7
- chartkick 4.2No known advisories in 4.2.1
- chartkick 4.1No known advisories in 4.1.3
- chartkick 4.0No known advisories in 4.0.5
- chartkick 3.4No known advisories in 3.4.2
- chartkick 3.31 advisory in 3.3.2
- chartkick 3.22 advisories in 3.2.2
- chartkick 3.13 advisories in 3.1.0
- chartkick 3.03 advisories in 3.0.2
Which of your client projects still run an old chartkick?
NPMscan reads the Gemfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other RubyGems packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.