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

The (1) jdom.rb and (2) rexml.rb components in Active Support in Ruby on Rails before 4.1.11 and 4.2.x before 4.2.2, when JDOM or REXML is e

The (1) jdom.rb and (2) rexml.rb components in Active Support in Ruby on Rails before 4.1.11 and 4.2.x before 4.2.2, when JDOM or REXML is enabled, allow remote attackers to cause a denial of service (SystemStackError) via a large XML document depth.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Jul 26, 2015
Updated
Jun 16, 2026
EPSS
4.3% · 91th percentile
CWE
—
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.3%

Affected systems

VendorProduct
opensuseopensuse
rubyonrailsrails

Affected versions

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

  • opensuse opensuse13.1
  • opensuse opensuse13.2
  • rubyonrails rails4.1.0
  • rubyonrails rails4.1.1
  • rubyonrails rails4.1.2
  • rubyonrails rails4.1.3
  • rubyonrails rails4.1.4
  • rubyonrails rails4.1.5
  • rubyonrails rails4.1.6
  • rubyonrails rails4.1.7
  • rubyonrails rails4.1.8
  • rubyonrails rails4.2.0
  • rubyonrails rails4.2.1

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12railsbefore 2:4.2.4-22:4.2.4-2
Debian:7ruby-activesupport-3.2before 3.2.6-6+deb7u23.2.6-6+deb7u2
Debian:8railsbefore 2:4.1.8-1+deb8u12:4.1.8-1+deb8u1
openSUSE:Tumbleweedrubygem-activesupport-4_2before 5.0.0.1-1.15.0.0.1-1.1
RubyGemsactivesupportfrom 4.0.0.beta1 · before 4.1.114.1.11
RubyGemsactivesupportfrom 4.2.0.beta1 · before 4.2.24.2.2
RubyGemsactivesupportbefore 3.2.223.2.22
SUSE:Linux Enterprise Software Development Kit 11 SP3rubygem-activesupport-3_2before 3.2.12-0.14.33.2.12-0.14.3
SUSE:OpenStack Cloud 5rubygem-activesupport-4_1before 4.1.9-9.24.1.9-9.2

Other highest-scoring records for the same primary product.

  • CVE-2013-4115Buffer overflow in the idnsALookup function in dns_internal.cc in Squid 3.2 through 3.2.11 and 3.3 through 3.3.6 allows remote attackers to
    43Plan
  • CVE-2015-7805Heap-based buffer overflow in libsndfile 1.0.25 allows remote attackers to have unspecified impact via the headindex value in the header in
    41Plan
  • CVE-2015-5957Buffer overflow in the DumpSysVar function in var.c in Remind before 3.1.15 allows attackers to have unspecified impact via a long name.
    41Plan
  • CVE-2008-2388Multiple off-by-one errors in opensuse-updater in openSUSE 10.2 have unspecified impact and attack vectors.
    40Plan
  • CVE-2016-2335The CInArchive::ReadFileItem method in Archive/Udf/UdfIn.cpp in 7zip 9.20 and 15.05 beta and p7zip allows remote attackers to cause a denial
    38Monitor
  • CVE-2016-1663The SerializedScriptValue::transferArrayBuffers function in WebKit/Source/bindings/core/v8/SerializedScriptValue.cpp in the V8 bindings in B
    35Monitor

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:rails2:4.2.4-2 · Debian:12Package registry (OSV)
debian:ruby-activesupport-3.23.2.6-6+deb7u2 · Debian:7Package registry (OSV)
opensuse:rubygem-activesupport-4_25.0.0.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
RubyGems:activesupport3.2.22Package registry (OSV)
RubyGems:activesupport4.1.11Package registry (OSV)
RubyGems:activesupport4.2.2Package registry (OSV)
suse:rubygem-activesupport-3_23.2.12-0.14.3 · SUSE:Linux Enterprise Software Development Kit 11 SP3Package registry (OSV)
suse:rubygem-activesupport-4_14.1.9-9.2 · SUSE:OpenStack Cloud 5Package 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
none
Integrity
none
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
None
Integrity impact
None
Availability impact
P

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

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