Skip to content
Noroxi
CVE-2015-1840· NVD / CVE Program· CNA redhat

jquery_ujs.js in jquery-rails before 3.1.3 and 4.x before 4.0.4 and rails.js in jquery-ujs before 1.0.4, as used with Ruby on Rails 3.x and

jquery_ujs.js in jquery-rails before 3.1.3 and 4.x before 4.0.4 and rails.js in jquery-ujs before 1.0.4, as used with Ruby on Rails 3.x and 4.x, allow remote attackers to bypass the Same Origin Policy, and trigger transmission of a CSRF token to a different-domain web server, via a leading space character in a URL within an attribute value.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Jul 26, 2015
Updated
Jun 16, 2026
EPSS
4.5% · 91th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.5%

Affected systems

VendorProduct
fedoraprojectfedora
rubyonrailsjquery-rails
rubyonrailsjquery-ujs
opensuseopensuse

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora21
  • fedoraproject fedora22
  • opensuse opensuse13.1
  • opensuse opensuse13.2
  • rubyonrails jquery-railsup to 3.1.2 inclusive
  • rubyonrails jquery-rails4.0.0
  • rubyonrails jquery-rails4.0.1
  • rubyonrails jquery-ujsup to 1.0.3 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12ruby-jquery-railsbefore 4.0.4-14.0.4-1
openSUSE:Tumbleweedruby3.2-rubygem-jquery-railsbefore 4.5.1-1.34.5.1-1.3
openSUSE:Tumbleweedrubygem-jquery-railsbefore 4.6.0-1.94.6.0-1.9
openSUSE:Tumbleweedrubygem-jquery-railsbefore 4.5.0-1.14.5.0-1.1
openSUSE:Tumbleweedrubygem-jquery-railsbefore 4.6.0-1.54.6.0-1.5
openSUSE:Tumbleweedrubygem-jquery-railsbefore 4.6.0-1.74.6.0-1.7
RubyGemsjquery-railsfrom 4.0.0 · before 4.0.44.0.4
RubyGemsjquery-railsbefore 3.1.33.1.3
RubyGemsjquery-ujsbefore 1.0.41.0.4

Other highest-scoring records for the same primary product.

  • CVE-2018-1111DHCP packages in Red Hat Enterprise Linux 6 and 7, Fedora 28, and earlier are vulnerable to a command injection flaw in the NetworkManager i
    59Plan
  • CVE-2024-24576Rusts's `std::process::Command` did not properly escape arguments of batch files on Windows
    46Plan
  • CVE-2016-7167Multiple integer overflows in the (1) curl_escape, (2) curl_easy_escape, (3) curl_unescape, and (4) curl_easy_unescape functions in libcurl
    43Plan
  • CVE-2016-2173org.springframework.core.serializer.DefaultDeserializer in Spring AMQP before 1.5.5 allows remote attackers to execute arbitrary code.
    41Plan
  • CVE-2015-0278libuv before 0.10.34 does not properly drop group privileges, which allows context-dependent attackers to gain privileges via unspecified ve
    41Plan
  • CVE-2015-3145The sanitize_cookie_path function in cURL and libcurl 7.31.0 through 7.41.0 does not properly calculate an index, which allows remote attack
    41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ruby-jquery-rails4.0.4-1 · Debian:12Package registry (OSV)
opensuse:ruby3.2-rubygem-jquery-rails4.5.1-1.3 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-jquery-rails4.5.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
RubyGems:jquery-rails3.1.3Package registry (OSV)
RubyGems:jquery-rails4.0.4Package registry (OSV)
RubyGems:jquery-ujs1.0.4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
Low
Confidentiality impact
P
Integrity impact
None
Availability impact
None

CVSS vector

AV:N/AC:L/Au:N/C:P/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records