First published: Fri Jul 29 2016(Updated: )
It was found that MongoDB creates a world-readable .dbshell history file in a user's directory: The mongodb client doesn't store authentication commands, but there's still information leakage, though, even if only about database and collection names, or data structure. As for data itself, the history could also contain sensitive information; for instance, if usernames for some other service were stored in a mongo collection, the history could contain lines like: db.users.find({user:"foo"}) or even: db.users.update({user:"foo"},{$set:{password:"OhComeOnNow"}}) Upstream bug (closed as "Works as Designed"): <a href="https://jira.mongodb.org/browse/SERVER-25335">https://jira.mongodb.org/browse/SERVER-25335</a> CVE request: <a href="http://seclists.org/oss-sec/2016/q3/199">http://seclists.org/oss-sec/2016/q3/199</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/mongodb | ||
debian/mongodb | <=1:2.4.10-5 | 1:2.6.12-3 1:3.2.11-1 1:2.4.10-5+deb8u1 |
debian/2.0.6-1 | ||
debian/2.4.10-5 | ||
MongoDB MongoDB | <3.0.15 | |
MongoDB MongoDB | >=3.2<3.2.14 | |
MongoDB MongoDB | >=3.3<3.3.14 | |
Fedoraproject Fedora | =25 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.