# CVE-2019-2708: Denial of service in Oracle Berkeley DB > A local attacker with low privileges can cause a partial denial of service in Oracle Berkeley DB Data Store. - **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Apr 2019 - **Updated:** 2 Oct 2024 - **Also known as:** ALSA-2021:1675, AZL-34927, AZL-6630, BELL-CVE-2019-2708, GHSA-4h5r-2hfh-8prm, MGASA-2021-0057, OESA-2021-1156, RHSA-2021:1675, RLSA-2021:1675, SUSE-SU-2022:4214-1, SUSE-SU-2022:4289-1, SUSE-SU-2025:20067-1, openSUSE-SU-2024:14246-1 ## What is CVE-2019-2708? CVE-2019-2708 is a low-severity denial of service vulnerability in Oracle Berkeley Db, published on 23 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Vulnerability in the Data Store component of Oracle Berkeley DB. Supported versions that are affected are Prior to 6.138, prior to 6.2.38 and prior to 18.1.32. Easily exploitable vulnerability allows low privileged attacker having Local Logon privilege with logon to the infrastructure where Data Store executes to compromise Data Store. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Data Store. CVSS 3.0 Base Score 3.3 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L). ## Which versions are affected by CVE-2019-2708? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libdb-cxx` | AlmaLinux:8 | All versions | 5.3.28-40.el8 | | `libdb-cxx-devel` | AlmaLinux:8 | All versions | 5.3.28-40.el8 | | `libdb-devel-doc` | AlmaLinux:8 | All versions | 5.3.28-40.el8 | | `libdb-sql` | AlmaLinux:8 | All versions | 5.3.28-40.el8 | | `libdb-sql-devel` | AlmaLinux:8 | All versions | 5.3.28-40.el8 | | `libdb-cxx-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.3.28-40.el8 | | `libdb-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.3.28-40.el8 | | `libdb-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.3.28-40.el8 | | `libdb-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.3.28-40.el8 | | `libdb-java-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.3.28-40.el8 | | `libdb-sql-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.3.28-40.el8 | | `libdb-sql-devel-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.3.28-40.el8 | | `libdb-tcl-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.3.28-40.el8 | | `libdb-utils-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.3.28-40.el8 | | `libdb` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.3.28-40.el8 | | `libdb-cxx-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.3.28-40.el8 | | `libdb-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.3.28-40.el8 | | `libdb-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.3.28-40.el8 | | `libdb-java-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.3.28-40.el8 | | `libdb-sql-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.3.28-40.el8 | | `libdb-sql-devel-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.3.28-40.el8 | | `libdb-tcl-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.3.28-40.el8 | | `libdb-utils` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.3.28-40.el8 | | `libdb-utils-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.3.28-40.el8 | | `libdb-cxx` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-cxx-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-cxx-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-devel-doc` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-java-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-sql` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-sql-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-sql-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-sql-devel-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-tcl-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb-utils-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.3.28-40.el8 | | `libdb` | Rocky Linux:8 | All versions | 0:5.3.28-40.el8 | | `libdb-4_8` | SUSE:Linux Enterprise Micro 5.1 | All versions | 4.8.30-150000.7.6.1 | | `libdb-4_8` | SUSE:Linux Enterprise Micro 5.2 | All versions | 4.8.30-150000.7.6.1 | Products: Oracle Berkeley Db. ## How do I fix CVE-2019-2708? Upgrade to a fixed version. ## Is CVE-2019-2708 being exploited? There is no known exploitation of CVE-2019-2708 in the wild and no public exploit code. ## Other vulnerabilities in Oracle Berkeley Db - [CVE-2016-0682](https://insights.sbomify.com/CVE-2016-0682/): Other in n/a (high 7.8) - [CVE-2016-0689](https://insights.sbomify.com/CVE-2016-0689/): Other in n/a (high 7.8) - [CVE-2016-0692](https://insights.sbomify.com/CVE-2016-0692/): Other in n/a (high 7.8) - [CVE-2016-0694](https://insights.sbomify.com/CVE-2016-0694/): Other in n/a (high 7.8) - [CVE-2016-3418](https://insights.sbomify.com/CVE-2016-3418/): Other in n/a (high 7.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-2708 and fix it if it is affected. What it is: CVE-2019-2708 is a low-severity denial of service vulnerability in Oracle Berkeley Db, published on 23 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-2708 in the wild and no public exploit code. Affected product: Oracle Berkeley Db. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-2708/ (Markdown: https://insights.sbomify.com/CVE-2019-2708/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-2708 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-2708 - OSV: https://osv.dev/vulnerability/CVE-2019-2708 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-2708/ Summaries are generated and may contain mistakes; the official description above is the record.