Bug 1324496 (CVE-2016-3104)

Summary: CVE-2016-3104 mongodb: Unauthenticated remote DoS via memory exhaustion
Product: [Other] Security Response Reporter: Adam Mariš <amaris>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: abaron, abhgupta, apevec, ayoung, bhu, bkearney, cbillett, ccoleman, chrisw, dallan, dmcphers, gkotton, iboverma, jialiu, joelsmith, jokerman, jorton, jross, jschluet, lhh, lmeyer, lpeer, markmc, matt, mcressma, mmaslano, mmccomas, mmccune, nthomas, ohadlevy, rbryant, sclewis, scorneli, security-response-team, sisharma, srevivo, tdecacqu, tiwillia, tlestach, tomckay, williams
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1403610    
Bug Blocks: 1324500    

Description Adam Mariš 2016-04-06 13:27:16 UTC
It was reported that it is possible for remote unauthenticated attackers to cause the host to kill mongoDB service due to memory exhaustion. This issue can be triggered by making multiple database creation requests. Even if authentication fails, the requested database is created in memory. Eventually, the host runs out of memory and kills Mongo service resulting in a denial of service. After service restart, all created databases are deleted.

The issue was identified in versions 2.4 and 2.6. The issue was found to be not reproducible on 3.0.11 and 3.2.4.

External references:

Comment 1 Adam Mariš 2016-04-06 13:27:42 UTC

Name: Simon Budail Essard, Philippe Jacquot

Comment 6 Huzaifa S. Sidhpurwala 2016-12-08 06:52:00 UTC
Public via:


Comment 8 Huzaifa S. Sidhpurwala 2016-12-08 07:55:23 UTC
Note on exploitation on mongodb-2.6:

This issue does not affect all MongoDB 2.6 installations; it only
affects MongoDB 2.6 installations in circumstances where they first had a
MongoDB 2.4 installation with authentication enabled, upgraded to 2.6, and
did not complete a full upgrade (i.e., did not migrate the
authuser-schema). More details are provided in the above SERVER ticket.