Bug 969560 (CVE-2013-2132) - CVE-2013-2132 pymongo: null pointer when decoding invalid DBRef
Summary: CVE-2013-2132 pymongo: null pointer when decoding invalid DBRef
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-2132
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 969563 969566 969569 969570 969571 969574 969582 969626 1165388
Blocks: 969581
TreeView+ depends on / blocked
 
Reported: 2013-05-31 19:34 UTC by Kurt Seifried
Modified: 2020-07-31 12:24 UTC (History)
27 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-17 05:43:47 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1170 normal SHIPPED_LIVE Important: mongodb and pymongo security and enhancement update 2013-08-21 21:27:48 UTC

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.


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