First published: Tue Aug 02 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>
Affected Software | Affected Version | How to fix |
---|---|---|
MongoDB |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1362553 is considered low, as it involves information leakage but does not expose authentication credentials.
To fix REDHAT-BUG-1362553, you can change the permissions of the .dbshell file to restrict access.
The risks associated with REDHAT-BUG-1362553 include potential exposure of sensitive database and collection names.
REDHAT-BUG-1362553 affects all versions of MongoDB that create a world-readable .dbshell history file.
Yes, a workaround for REDHAT-BUG-1362553 is to manually set the file permissions of the .dbshell history file after its creation.