First published: Wed Apr 06 2016(Updated: )
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: <a href="https://jira.mongodb.org/browse/SERVER-24378">https://jira.mongodb.org/browse/SERVER-24378</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
MongoDB Server | =2.4.0 | |
MongoDB Server | =2.6.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-3104 is considered a medium severity vulnerability due to its potential for remote denial of service.
To mitigate CVE-2016-3104, ensure that proper input validation is implemented to limit database creation requests from unauthenticated users.
CVE-2016-3104 affects MongoDB versions 2.4.0 and 2.6.0.
CVE-2016-3104 enables remote unauthenticated attackers to exhaust memory, potentially causing the MongoDB service to crash.
The recommended solution for CVE-2016-3104 is to upgrade to a version of MongoDB that is not affected by this vulnerability.