First published: Wed Jan 08 2014(Updated: )
MongoDB was found to be affected by a memory over-read bug that can be used by an authenticated user (if applicable) to obtain raw MongoDB server process memory contents via incorrect BSON object length. This issue does not seem to cross a security boundary under most deployments, but for some it could, like differently-privileged MongoDB users, data already deleted from the DB yet staying in process memory, or/and metadata that is not normally retrievable. References: <a href="http://seclists.org/oss-sec/2014/q1/27">http://seclists.org/oss-sec/2014/q1/27</a> <a href="http://blog.ptsecurity.com/2012/11/attacking-mongodb.html">http://blog.ptsecurity.com/2012/11/attacking-mongodb.html</a> <a href="https://github.com/cyberpunkych/attacking_mongodb">https://github.com/cyberpunkych/attacking_mongodb</a> (The files used for the attack demonstration.)
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/mongodb | <2.3.2 | 2.3.2 |
MongoDB MongoDB | <=2.3.1 | |
MongoDB MongoDB | =1.2.0 | |
MongoDB MongoDB | =1.4.0 | |
MongoDB MongoDB | =1.6.0 | |
MongoDB MongoDB | =1.8.0 | |
MongoDB MongoDB | =2.0.0 | |
MongoDB MongoDB | =2.0.1 | |
MongoDB MongoDB | =2.0.2 | |
MongoDB MongoDB | =2.0.3 | |
MongoDB MongoDB | =2.0.4 | |
MongoDB MongoDB | =2.0.5 | |
MongoDB MongoDB | =2.0.6 | |
MongoDB MongoDB | =2.0.7 | |
MongoDB MongoDB | =2.0.8 | |
MongoDB MongoDB | =2.2.0 | |
MongoDB MongoDB | =2.2.1 | |
MongoDB MongoDB | =2.2.2 | |
MongoDB MongoDB | =2.2.3 | |
MongoDB MongoDB | =2.2.4 | |
MongoDB MongoDB | =2.2.5 | |
MongoDB MongoDB | =2.2.6 | |
MongoDB MongoDB | =2.2.7 | |
MongoDB MongoDB | =2.3.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.