World-readable .dbshell history file in mongodb

mongodb Updated 02 Oct 2025

Summary

09/08/2016
N/A
Yes i
Unrated
Not published

DLA-588-2: mongodb - regression update. Affects mongodb versions < 1:2.0.6-1.1+deb7u1. Fixed in 1:2.0.6-1.1+deb7u1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

MongoDB is a popular open-source NoSQL database management system. It provides high performance, scalability, and flexibility for storing and retrieving data. The vulnerability in MongoDB version 2.0.6-1+deb7u1 for Debian 7 Wheezy allows the .dbshell history file to be world-readable, potentially exposing sensitive information.

Vulnerability Detail

The vulnerability, identified as CVE-2016-6494, arises from the world-readable .dbshell history file. This file contains a history of commands executed in the MongoDB shell, including potentially sensitive information such as database credentials. An attacker with access to the file can retrieve this information and use it for malicious purposes. This vulnerability poses a risk to the confidentiality and integrity of the MongoDB deployment.

How To Fix

Minimum fixed version

1:2.0.6-1.1+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade mongodb

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, upgrading to the fixed version is the recommended solution.

Conclusion

The world-readable .dbshell history file vulnerability in MongoDB version 2.0.6-1+deb7u1 for Debian 7 Wheezy can lead to unauthorized access to sensitive information. To mitigate this vulnerability, it is crucial to upgrade to the fixed version of MongoDB. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for mongodb →

Share this vulnerability

FAQ

The vulnerability allows unauthorized access to the .dbshell history file, potentially exposing sensitive information such as database credentials.

Users of MongoDB version 2.0.6-1+deb7u1 for Debian 7 Wheezy are affected by this vulnerability.

There is no known exploit for this vulnerability at the moment.

The recommended mitigation is to upgrade to the fixed version of MongoDB (2.0.6-1+deb7u1 or later).

You can find more information about this vulnerability in the Debian LTS security advisories and the CVE-2016-6494 entry.

Related vulnerabilities

Recent vulnerabilities recorded for mongodb.

How To Fix

Minimum fixed version

1:2.0.6-1.1+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade mongodb

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback