Advisory Published
Advisory Published
Updated

CVE-2015-3227

First published: Sun Jul 26 2015(Updated: )

The (1) `jdom.rb` and (2) `rexml.rb` components in Active Support in Ruby on Rails before 3.2.22, 4.1.x 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.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
SUSE Linux=13.1
SUSE Linux=13.2
Ruby on Rails=4.1.0
Ruby on Rails=4.1.1
Ruby on Rails=4.1.2
Ruby on Rails=4.1.3
Ruby on Rails=4.1.4
Ruby on Rails=4.1.5
Ruby on Rails=4.1.6
Ruby on Rails=4.1.7
Ruby on Rails=4.1.8
Ruby on Rails=4.2.0
Ruby on Rails=4.2.1
rubygems/activesupport<3.2.22
3.2.22
rubygems/activesupport>=4.2.0.beta1<4.2.2
4.2.2
rubygems/activesupport>=4.0.0.beta1<4.1.11
4.1.11
openSUSE=13.1
openSUSE=13.2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2015-3227?

    CVE-2015-3227 is classified as a denial of service vulnerability that can lead to a SystemStackError.

  • How do I fix CVE-2015-3227?

    To fix CVE-2015-3227, upgrade Ruby on Rails to version 4.1.11 or 4.2.2 and later.

  • Which versions of Ruby on Rails are affected by CVE-2015-3227?

    CVE-2015-3227 affects Ruby on Rails versions prior to 4.1.11 and 4.2.x before 4.2.2.

  • Can CVE-2015-3227 be exploited remotely?

    Yes, CVE-2015-3227 can be exploited remotely by sending a large XML document that causes a denial of service.

  • What components of Ruby on Rails are vulnerable in CVE-2015-3227?

    The vulnerable components are jdom.rb and rexml.rb in the Active Support library.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203