[SERVER-7769] use --objcheck by default, Server arbitrary memory reading Created: 27/Nov/12 Updated: 11/Jul/16 Resolved: 20/Dec/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yury | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
The specialists of the Positive Research center have detected "Server arbitrary memory reading" vulnerability in MongoDB application. Cause of incorrect execution of BSON-document length in column name in the insert command it’s possible to insert a record which can contain a base64-encrypted server memory chunks. Example of use: Suppose you have a table "dropme" with write permission. Execute the following command with a result: > db.dropme.insert( {"\x16\x00\x00\x00\x05hello\x00\x010\x00\x00\x00world\x00\x00" : "world"}) After base64-code decryption you can get bytes from random server memory chunks. Credits The vulnerability was discovered by Mikhail Firstov, Positive Research Center (Positive Technologies Company) |
| Comments |
| Comment by auto [ 20/Dec/12 ] |
|
Author: {u'date': u'2012-12-20T03:15:03Z', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}Message: |
| Comment by auto [ 18/Dec/12 ] |
|
Author: {u'date': u'2012-12-18T14:40:08Z', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |