Bug 969560 - (CVE-2013-2132) CVE-2013-2132 pymongo: null pointer when decoding invalid DBRef
CVE-2013-2132 pymongo: null pointer when decoding invalid DBRef
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 969563 969566 969569 969570 969571 969574 969582 969626 1165388
Blocks: 969581
  Show dependency treegraph
Reported: 2013-05-31 15:34 EDT by Kurt Seifried
Modified: 2015-01-17 00:43 EST (History)
27 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-01-17 00:43:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker 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 17:27:48 EDT

  None (edit)
Description Kurt Seifried 2013-05-31 15:34:15 EDT
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

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

External reference:

Upstream patch:
Comment 1 Kurt Seifried 2013-05-31 15:38:48 EDT
Created mongodb tracking bugs for this issue

Affects: epel-all [bug 969563]
Comment 2 Kurt Seifried 2013-05-31 15:39:44 EDT
Created mongodb tracking bugs for this issue

Affects: fedora-all [bug 969566]
Comment 8 errata-xmlrpc 2013-08-21 13:30:06 EDT
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 15:30:18 EDT

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.