CVE-2015-1840: jquery-rails and jquery-ujs subject to Exposure of Sensitive Information

CVE-2015-1840 · Severity: info · Published 2017-10-24

jquery-rails and jquery-ujs subject to Exposure of Sensitive Information

Technologies: jquery-rails (RubyGems). Vendors: RubyGems.

Quick answers

Is CVE-2015-1840 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2015-1840 being exploited in the wild.
How severe is CVE-2015-1840?
Informational severity, published 24 October 2017.
Which products and versions are affected?
jquery-rails (RubyGems) ECOSYSTEM:introduced=0,fixed=3.1.3; jquery-ujs (RubyGems) ECOSYSTEM:introduced=0,fixed=1.0.4.
Is there a fix for CVE-2015-1840?
Yes. jquery-rails (RubyGems): upgrade to 3.1.3 or later; jquery-ujs (RubyGems): upgrade to 1.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2015-1840?
Check whether you run jquery-rails (RubyGems) or jquery-ujs (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • jquery-rails (RubyGems): upgrade to 3.1.3 or later
    bundle update jquery-rails
  • jquery-ujs (RubyGems): upgrade to 1.0.4 or later
    bundle update jquery-ujs

Affected products

  • jquery-rails (RubyGems) ECOSYSTEM:introduced=0,fixed=3.1.3
  • jquery-ujs (RubyGems) ECOSYSTEM:introduced=0,fixed=1.0.4

Identifiers

  • CVE-2015-1840
  • GHSA-4whc-pp4x-9pf3

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.