CVE-2016-0694: Unspecified vulnerability in Oracle Berkeley DB

db Updated 02 Oct 2025

Summary

21/04/2016
N/A
Yes i
High
7.8

CVE-2016-0694: Unspecified vulnerability in the DataStore component in Oracle Berkeley DB 11.2.5.0.32, 11.2.5.1.29, 11.2.5.2.42, 11.2.5.3.28, 12.1.6.0.35, and 12.1.6.1.26 allows local users to affect confidentiality, integrity, and ava... Affects db versions < 0. No fix is published. 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

Oracle Berkeley DB is a high-performance embedded database library that provides scalable data management services to applications. It is widely used in various software systems. This vulnerability affects versions 11.2.5.0.32, 11.2.5.1.29, 11.2.5.2.42, 11.2.5.3.28, 12.1.6.0.35, and 12.1.6.1.26 of Oracle Berkeley DB. The vulnerability allows local users to impact the confidentiality, integrity, and availability of the system. It is a separate vulnerability from CVE-2016-0682, CVE-2016-0689, CVE-2016-0692, and CVE-2016-3418.

Vulnerability Detail

The specific details of this vulnerability are unspecified. However, it is known that the vulnerability resides in the DataStore component of Oracle Berkeley DB. The impact of the vulnerability can result in the compromise of confidentiality, integrity, and availability of the affected system. The exact vectors of attack are unknown at this time.

How To Fix

To fix this vulnerability, it is recommended to update Oracle Berkeley DB to a version that includes a fix for this specific issue. The latest version of Oracle Berkeley DB should be consulted to ensure the vulnerability is properly addressed.

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

Workaround

No specific workaround has been provided for this vulnerability.

Conclusion

CVE-2016-0694 is an unspecified vulnerability in Oracle Berkeley DB that can impact the confidentiality, integrity, and availability of the system. It is recommended to update Oracle Berkeley DB to a fixed version to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for db →

Share this vulnerability

FAQ

Oracle Berkeley DB is a high-performance embedded database library used by many applications.

Versions 11.2.5.0.32, 11.2.5.1.29, 11.2.5.2.42, 11.2.5.3.28, 12.1.6.0.35, and 12.1.6.1.26 are affected.

The vulnerability can result in the compromise of confidentiality, integrity, and availability of the system.

No specific exploits have been disclosed for this vulnerability at this time.

Updating Oracle Berkeley DB to a version that includes a fix for this vulnerability is the recommended course of action.

Related vulnerabilities

Recent vulnerabilities recorded for db.

How To Fix

To fix this vulnerability, it is recommended to update Oracle Berkeley DB to a version that includes a fix for this specific issue. The latest version of Oracle Berkeley DB should be consulted to ensure the vulnerability is properly addressed.

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