Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1324496 - (CVE-2016-3104) CVE-2016-3104 mongodb: Unauthenticated remote DoS via memory exhaustion
CVE-2016-3104 mongodb: Unauthenticated remote DoS via memory exhaustion
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20161206,repor...
: Security
Depends On: 1403610
Blocks: 1324500
  Show dependency treegraph
 
Reported: 2016-04-06 09:27 EDT by Adam Mariš
Modified: 2018-06-29 18:08 EDT (History)
47 users (show)

See Also:
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: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2016-04-06 09:27:16 EDT
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:
https://jira.mongodb.org/browse/SERVER-24378
Comment 1 Adam Mariš 2016-04-06 09:27:42 EDT
Acknowledgments:

Name: Simon Budail Essard, Philippe Jacquot
Comment 6 Huzaifa S. Sidhpurwala 2016-12-08 01:52:00 EST
Public via:

https://jira.mongodb.org/browse/SERVER-24378
Comment 8 Huzaifa S. Sidhpurwala 2016-12-08 02:55:23 EST
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.

https://jira.mongodb.org/browse/SERVER-24378

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