Security Update for db4.7

db4.7 Updated 02 Oct 2025

Summary

18/10/2017
N/A
Yes i
Unrated
Not published

DLA-1137-1: db4.7 - security update. Affects db4.7 versions < 4.7.25-21+deb7u1. Fixed in 4.7.25-21+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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

db4.7 is a database management system that provides key-value storage for applications. It is widely used in various software applications and systems. However, a vulnerability has been discovered in db4.7 that could lead to information leakage.

Vulnerability Detail

The vulnerability in db4.7 arises from the fact that it reads the DB_CONFIG file from the current working directory. This can be exploited by malicious actors to trick privileged processes into reading arbitrary files, potentially leading to the disclosure of sensitive information. The impact of this vulnerability can be significant, as it allows unauthorized access to files that should not be accessible.

How To Fix

Minimum fixed version

4.7.25-21+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade db4.7

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, users can mitigate the risk by ensuring that the current working directory of privileged processes does not contain any sensitive files that could be accessed by unauthorized parties.

Conclusion

In conclusion, the db4.7 package is vulnerable to information leakage due to the way it reads the DB_CONFIG file. To mitigate this vulnerability, it is crucial to upgrade to the latest version of the package. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for db4.7 →

Share this vulnerability

FAQ

db4.7 is a database management system that provides key-value storage for applications. It is widely used in various software applications and systems.

The vulnerability allows unauthorized access to files that should not be accessible, potentially leading to the disclosure of sensitive information.

To fix this vulnerability, you should upgrade the db4.7 package to version 4.7.25-21+deb7u1 or later.

There is no specific workaround mentioned for this vulnerability. However, you can mitigate the risk by ensuring that the current working directory of privileged processes does not contain any sensitive files.

You can find more information about Debian LTS security advisories, including how to apply updates and frequently asked questions, on the Debian LTS wiki.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

4.7.25-21+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade db4.7

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