Bug 969560 (CVE-2013-2132)

Summary: CVE-2013-2132 pymongo: null pointer when decoding invalid DBRef
Product: [Other] Security Response Reporter: Kurt Seifried <kseifried>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: admiller, bkearney, bleanhar, bretm, ccoleman, cpelland, dajohnso, dmcphers, esammons, iboverma, jeckersb, jialiu, jim, jlieskov, johan.o.hedin, jrusnack, jslagle, katello-bugs, lmeyer, mcressma, mmccune, mmcgrath, morazi, mrg-program-list, nathaniel, tdawson, whayutin
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-17 05:43:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 969563, 969566, 969569, 969570, 969571, 969574, 969582, 969626, 1165388    
Bug Blocks: 969581    

Description Kurt Seifried 2013-05-31 19:34:15 UTC
A user triggerable null pointer occurs when parsing invalid DBref records. 
This was reported by Jibbers McGee.

This can be triggered in Mongo shell:
db.python532.insert({x : {"$ref" : "whatever"} });

Or in Python shell:
import pymongo
pymongo.MongoClient().test.python532.find_one()

A workaround is reportedly available:
Add "process_dbrefs=False" to all the drivers

External reference:
https://jira.mongodb.org/browse/PYTHON-532

Upstream patch:
https://github.com/mongodb/mongo-python-driver/commit/a060c15ef87e0f0e72974c7c0e57fe811bbd06a2

Comment 1 Kurt Seifried 2013-05-31 19:38:48 UTC
Created mongodb tracking bugs for this issue

Affects: epel-all [bug 969563]

Comment 2 Kurt Seifried 2013-05-31 19:39:44 UTC
Created mongodb tracking bugs for this issue

Affects: fedora-all [bug 969566]

Comment 8 errata-xmlrpc 2013-08-21 17:30:06 UTC
This issue has been addressed in following products:

  MRG for RHEL-6 v.2

Via RHSA-2013:1170 https://rhn.redhat.com/errata/RHSA-2013-1170.html

Comment 9 Kurt Seifried 2014-08-08 19:30:18 UTC
Statement:

Red Hat Update Infrastructure 2.1.3 is now in Production 2 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Update Infrastructure Life Cycle: https://access.redhat.com/support/policy/updates/rhui.