Bug 917236 (CVE-2013-1800) - CVE-2013-1800 rubygem-crack: YAML parameter parsing vulnerability
Summary: CVE-2013-1800 rubygem-crack: YAML parameter parsing vulnerability
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-1800
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 917237 917238 917239 917240 917241 1030770
Blocks: 917245 1028279
TreeView+ depends on / blocked
 
Reported: 2013-03-02 08:59 UTC by Kurt Seifried
Modified: 2019-09-29 13:01 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-15 04:43:56 UTC
Embargoed:


Attachments (Terms of Use)

Description Kurt Seifried 2013-03-02 08:59:52 UTC
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>". 

Vulnerable: <= 0.3.1
Fixed in: 0.3.2

Upstream fix:

https://github.com/jnunemaker/crack/commit/e3da1212a1f84a898ee3601336d1dbbf118fb5f6

References:

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

Comment 1 Kurt Seifried 2013-03-02 09:02:31 UTC
Created rubygem-crack tracking bugs for this issue

Affects: epel-all [bug 917237]

Comment 2 Kurt Seifried 2013-03-02 09:03:15 UTC
Created rubygem-crack tracking bugs for this issue

Affects: fedora-all [bug 917238]

Comment 5 Kurt Seifried 2013-07-26 06:20:19 UTC
Statement removed due to typo.


Note You need to log in before you can comment on or make changes to this bug.