# CVE-2023-39976: Memory corruption in n/a > A buffer overflow in libqb allows attackers to execute arbitrary code or cause denial of service via long log messages. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 Aug 2023 - **Updated:** 15 Oct 2024 - **Also known as:** ALSA-2023:6578, AZL-27859, AZL-36957, CLSA-2025-1762182516, CLSA-2026-1791385137, DEBIAN-CVE-2023-39976, GHSA-4fvg-53ww-3r5g, MGASA-2023-0339, RHSA-2023:5597, RHSA-2023:6578, RHSA-2023:7376, SUSE-SU-2023:3727-1, SUSE-SU-2023:3728-1, SUSE-SU-2023:3897-1, SUSE-SU-2023:3944-1, UBUNTU-CVE-2023-39976, USN-6308-1, openSUSE-SU-2024:13450-1 ## What is CVE-2023-39976? CVE-2023-39976 is a critical memory corruption vulnerability in n/a, published on 8 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description log_blackbox.c in libqb before 2.0.8 allows a buffer overflow via long log messages because the header size is not considered. Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2023-39976? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libqb` | AlmaLinux:9 | All versions | 2.0.6-4.el9_3 | | `libqb-devel` | AlmaLinux:9 | All versions | 2.0.6-4.el9_3 | | `doxygen2man-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.6-4.el9_3 | | `libqb` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.6-4.el9_3 | | `libqb-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.6-4.el9_3 | | `libqb-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.6-4.el9_3 | | `libqb-tests-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.0.6-4.el9_3 | | `doxygen2man-debuginfo` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:2.0.6-4.el9_3 | | `libqb-debuginfo` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:2.0.6-4.el9_3 | | `libqb-debugsource` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:2.0.6-4.el9_3 | | `libqb-devel` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:2.0.6-4.el9_3 | | `libqb-tests-debuginfo` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:2.0.6-4.el9_3 | | `doxygen2man-debuginfo` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:2.0.6-4.el9_3 | | `libqb-debuginfo` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:2.0.6-4.el9_3 | | `libqb-debugsource` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:2.0.6-4.el9_3 | | `libqb-devel` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:2.0.6-4.el9_3 | | `libqb-tests-debuginfo` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:2.0.6-4.el9_3 | | `doxygen2man-debuginfo` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:2.0.3-12.el9_0 | | `libqb` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:2.0.3-12.el9_0 | | `libqb-debuginfo` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:2.0.3-12.el9_0 | | `libqb-debugsource` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:2.0.3-12.el9_0 | | `libqb-tests-debuginfo` | Red Hat:rhel_eus:9.0::appstream | All versions | 0:2.0.3-12.el9_0 | | `doxygen2man-debuginfo` | Red Hat:rhel_eus:9.0::highavailability | All versions | 0:2.0.3-12.el9_0 | | `libqb-debuginfo` | Red Hat:rhel_eus:9.0::highavailability | All versions | 0:2.0.3-12.el9_0 | | `libqb-debugsource` | Red Hat:rhel_eus:9.0::highavailability | All versions | 0:2.0.3-12.el9_0 | | `libqb-devel` | Red Hat:rhel_eus:9.0::highavailability | All versions | 0:2.0.3-12.el9_0 | | `libqb-tests-debuginfo` | Red Hat:rhel_eus:9.0::highavailability | All versions | 0:2.0.3-12.el9_0 | | `doxygen2man-debuginfo` | Red Hat:rhel_eus:9.0::resilientstorage | All versions | 0:2.0.3-12.el9_0 | | `libqb-debuginfo` | Red Hat:rhel_eus:9.0::resilientstorage | All versions | 0:2.0.3-12.el9_0 | | `libqb-debugsource` | Red Hat:rhel_eus:9.0::resilientstorage | All versions | 0:2.0.3-12.el9_0 | | `libqb-devel` | Red Hat:rhel_eus:9.0::resilientstorage | All versions | 0:2.0.3-12.el9_0 | | `libqb-tests-debuginfo` | Red Hat:rhel_eus:9.0::resilientstorage | All versions | 0:2.0.3-12.el9_0 | | `doxygen2man-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:2.0.6-3.el9_2 | | `libqb` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:2.0.6-3.el9_2 | | `libqb-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:2.0.6-3.el9_2 | | `libqb-debugsource` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:2.0.6-3.el9_2 | | `libqb-tests-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:2.0.6-3.el9_2 | | `doxygen2man-debuginfo` | Red Hat:rhel_eus:9.2::highavailability | All versions | 0:2.0.6-3.el9_2 | | `libqb-debuginfo` | Red Hat:rhel_eus:9.2::highavailability | All versions | 0:2.0.6-3.el9_2 | | `libqb-debugsource` | Red Hat:rhel_eus:9.2::highavailability | All versions | 0:2.0.6-3.el9_2 | Products: Clusterlabs Libqb. ## How do I fix CVE-2023-39976? Upgrade to a fixed version. ## Is CVE-2023-39976 being exploited? There is no known exploitation of CVE-2023-39976 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2019-12779](https://insights.sbomify.com/CVE-2019-12779/): Path traversal in n/a (high 7.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-39976 and fix it if it is affected. What it is: CVE-2023-39976 is a critical memory corruption vulnerability in n/a, published on 8 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-39976 in the wild and no public exploit code. Affected product: n/a. 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-2023-39976/ (Markdown: https://insights.sbomify.com/CVE-2023-39976/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-39976 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-39976 - OSV: https://osv.dev/vulnerability/CVE-2023-39976 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-39976/ Summaries are generated and may contain mistakes; the official description above is the record.