[SERVER-10538] Passing $where predicate to db.currentOp() crashes mongod Created: 16/Aug/13 Updated: 11/Jul/16 Resolved: 09/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.2.5, 2.4.5 |
| Fix Version/s: | 2.2.7, 2.4.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Issue Status as of December 30th, 2013 ISSUE SUMMARY USER IMPACT
SOLUTION
WORKAROUNDS PATCHES Using a $where predicate with db.currentOp() on mongod causes a null dereference. Matcher::parseWhere() accesses the current context to look up which namespace to pass to the Where constructor, but cc()->_context is null, since db.currentOp() never sets a context.
Verified affects 2.2.5 and 2.4.5, and does not affect 2.0.9 and 2.5.1. |
| Comments |
| Comment by Githook User [ 09/Dec/13 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Githook User [ 09/Dec/13 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |