CVE-2013-1801: High severity John Nunemaker Httparty vulnerability

Published Mar 2, 2013
·
Updated

Tasha Drew reports:

Researchers investigating the Rails parameter parsing vulnerability discovered that the same or similar vulnerable code had made its way into multiple other libraries. If your application uses these libraries to process untrusted data, it may still be vulnerable even if you have upgraded Rails. Check your Gemfile and Gemfile.lock for vulnerable versions of the following libraries, and if you are using one, update it immediately.

You can update each of these by using "bundle update <gem name>". httparty

Vulnerable: <= 0.9.0

Fixed: 0.10.0

External references: https://support.cloud.engineyard.com/entries/22915701-january-14-2013-security-vulnerabilities-httparty-extlib-crack-nori-update-these-gems-immediately

https://github.com/jnunemaker/httparty/commit/53a812426dd32108d6cba4272b493aa03bc8c031

https://rubygems.org/gems/httparty/

Other sources

The httparty gem 0.9.0 and earlier for Ruby does not properly restrict casts of string values, which might allow remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) by leveraging Action Pack support for YAML type conversion, a similar vulnerability to CVE-2013-0156.

Affected Software

93 affected componentsFixes available
rubygems/httparty<=0.9.0
0.10.0
John Nunemaker Httparty<=0.9.0
John Nunemaker Httparty=0.1.0
John Nunemaker Httparty=0.1.1
John Nunemaker Httparty=0.1.2
John Nunemaker Httparty=0.1.3
John Nunemaker Httparty=0.1.5
John Nunemaker Httparty=0.1.6
John Nunemaker Httparty=0.1.7
John Nunemaker Httparty=0.1.8
John Nunemaker Httparty=0.2.0
John Nunemaker Httparty=0.2.1
John Nunemaker Httparty=0.2.2
John Nunemaker Httparty=0.2.3
John Nunemaker Httparty=0.2.4
John Nunemaker Httparty=0.2.5
John Nunemaker Httparty=0.2.6
John Nunemaker Httparty=0.2.7
John Nunemaker Httparty=0.2.8
John Nunemaker Httparty=0.2.9
John Nunemaker Httparty=0.2.10
John Nunemaker Httparty=0.3.0
John Nunemaker Httparty=0.3.1
John Nunemaker Httparty=0.4.0
John Nunemaker Httparty=0.4.1
John Nunemaker Httparty=0.4.2
John Nunemaker Httparty=0.4.3
John Nunemaker Httparty=0.4.4
John Nunemaker Httparty=0.4.5
John Nunemaker Httparty=0.5.0
John Nunemaker Httparty=0.5.1
John Nunemaker Httparty=0.5.2
John Nunemaker Httparty=0.6.0
John Nunemaker Httparty=0.6.1
John Nunemaker Httparty=0.7.0
John Nunemaker Httparty=0.7.1
John Nunemaker Httparty=0.7.2
John Nunemaker Httparty=0.7.3
John Nunemaker Httparty=0.7.4
John Nunemaker Httparty=0.7.5
John Nunemaker Httparty=0.7.6
John Nunemaker Httparty=0.7.7
John Nunemaker Httparty=0.7.8
John Nunemaker Httparty=0.8.0
John Nunemaker Httparty=0.8.1
John Nunemaker Httparty=0.8.2
John Nunemaker Httparty=0.8.3
jnunemaker httparty<=0.9.0
jnunemaker httparty=0.1.0
jnunemaker httparty=0.1.1
jnunemaker httparty=0.1.2
jnunemaker httparty=0.1.3
jnunemaker httparty=0.1.5
jnunemaker httparty=0.1.6
jnunemaker httparty=0.1.7
jnunemaker httparty=0.1.8
jnunemaker httparty=0.2.0
jnunemaker httparty=0.2.1
jnunemaker httparty=0.2.2
jnunemaker httparty=0.2.3
jnunemaker httparty=0.2.4
jnunemaker httparty=0.2.5
jnunemaker httparty=0.2.6
jnunemaker httparty=0.2.7
jnunemaker httparty=0.2.8
jnunemaker httparty=0.2.9
jnunemaker httparty=0.2.10
jnunemaker httparty=0.3.0
jnunemaker httparty=0.3.1
jnunemaker httparty=0.4.0
jnunemaker httparty=0.4.1
jnunemaker httparty=0.4.2
jnunemaker httparty=0.4.3
jnunemaker httparty=0.4.4
jnunemaker httparty=0.4.5
jnunemaker httparty=0.5.0
jnunemaker httparty=0.5.1
jnunemaker httparty=0.5.2
jnunemaker httparty=0.6.0
jnunemaker httparty=0.6.1
jnunemaker httparty=0.7.0
jnunemaker httparty=0.7.1
jnunemaker httparty=0.7.2
jnunemaker httparty=0.7.3
jnunemaker httparty=0.7.4
jnunemaker httparty=0.7.5
jnunemaker httparty=0.7.6
jnunemaker httparty=0.7.7
jnunemaker httparty=0.7.8
jnunemaker httparty=0.8.0
jnunemaker httparty=0.8.1
jnunemaker httparty=0.8.2
jnunemaker httparty=0.8.3

Remediation

Patch Available

https://github.com/jnunemaker/httparty/commit/53a812426dd32108d6cba4272b493aa03bc8c031

Event History

Mar 2, 2013
Data Sourced
via Red Hat·08:47 AM
DescriptionSeverityAffected Software
Apr 9, 2013
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description
Data Sourced
via NVD·08:55 PM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 24, 2017
Advisory Published
06:33 PM

Frequently Asked Questions

1

What is the severity of CVE-2013-1801?

CVE-2013-1801 is classified as a moderate severity vulnerability, which could lead to security risks if untrusted data is processed.

2

How do I fix CVE-2013-1801?

To fix CVE-2013-1801, update to the latest version of the HTTParty library that addresses this vulnerability.

3

Which versions of HTTParty are affected by CVE-2013-1801?

CVE-2013-1801 affects HTTParty versions up to and including 0.9.0.

4

What impact does CVE-2013-1801 have on applications?

Applications using vulnerable versions of HTTParty may inadvertently process untrusted data, potentially leading to attacks.

5

Is CVE-2013-1801 still a concern for current applications?

If your application is using a version of HTTParty prior to the patched versions, CVE-2013-1801 remains a significant security concern.

Company

Resources

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203