Unspecified vulnerability in Oracle Berkeley DB

db Updated 02 Oct 2025

Summary

21/04/2016

Disclosed on

N/A

Severity

Yes i

Fix available

High

Severity

7.8

CVSS Score

CVE-2016-0689: 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 Browse

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.

Background

Oracle Berkeley DB is a high-performance, transactional storage engine that provides key-value data management for applications. It is widely used in various software systems for its reliability and efficiency. However, a vulnerability has been discovered in 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.

Vulnerability Detail

The vulnerability, identified as CVE-2016-0689, is an unspecified flaw in the DataStore component of Oracle Berkeley DB. It allows local users to impact the confidentiality, integrity, and availability of the system through unknown vectors. This vulnerability is distinct from CVE-2016-0682, CVE-2016-0692, CVE-2016-0694, and CVE-2016-3418. The exact technical details and potential consequences of this vulnerability are not disclosed.

How To Fix

To fix this vulnerability, it is recommended to update Oracle Berkeley DB to a patched version provided by the vendor. The updated version should address the undisclosed vulnerability and ensure the security and stability of the system.

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

In conclusion, an unspecified vulnerability has been discovered in Oracle Berkeley DB 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. This vulnerability allows local users to impact the confidentiality, integrity, and availability of the system. It is recommended to update to a patched version to mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for db →