# CVE-2024-1062: Memory corruption in Red Hat Directory Server 11.5 E4S for RHEL 8 > A heap overflow in 389-ds-base allows attackers to cause a denial of service by writing values larger than 256 characters to log_entry_attr. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **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:** 12 Feb 2024 - **Updated:** 25 Feb 2026 - **Also known as:** ALSA-2024:3047, DEBIAN-CVE-2024-1062, GHSA-6v6c-gc45-x65c, OESA-2024-1148, RHSA-2024:1074, RHSA-2024:1372, RHSA-2024:3047, RLSA-2024:3047, SUSE-SU-2024:0908-1, SUSE-SU-2024:1906-1, UBUNTU-CVE-2024-1062 ## What is CVE-2024-1062? CVE-2024-1062 is a medium-severity memory corruption vulnerability in Fedoraproject Fedora, published on 12 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A heap overflow flaw was found in 389-ds-base. This issue leads to a denial of service when writing a value larger than 256 chars in log_entry_attr. Weakness: CWE-122 (Heap-based Buffer Overflow) ## Which versions are affected by CVE-2024-1062? It affects 13 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `389-ds-base` | AlmaLinux:8 | All versions | 1.4.3.39-3.module_el8.10.0+3829+ea459e35 | | `389-ds-base-devel` | AlmaLinux:8 | All versions | 1.4.3.39-3.module_el8.10.0+3829+ea459e35 | | `389-ds-base-legacy-tools` | AlmaLinux:8 | All versions | 1.4.3.39-3.module_el8.10.0+3829+ea459e35 | | `389-ds-base-libs` | AlmaLinux:8 | All versions | 1.4.3.39-3.module_el8.10.0+3829+ea459e35 | | `389-ds-base-snmp` | AlmaLinux:8 | All versions | 1.4.3.39-3.module_el8.10.0+3829+ea459e35 | | `python3-lib389` | AlmaLinux:8 | All versions | 1.4.3.39-3.module_el8.10.0+3829+ea459e35 | | `389-ds-base` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `389-ds-base-debuginfo` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `389-ds-base-debugsource` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `389-ds-base-devel` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `389-ds-base-legacy-tools` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `389-ds-base-legacy-tools-debuginfo` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `389-ds-base-libs` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `389-ds-base-libs-debuginfo` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `389-ds-base-snmp` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `389-ds-base-snmp-debuginfo` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `cockpit-389-ds` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `python3-lib389` | Red Hat:directory_server:11.7::el8 | All versions | 0:1.4.3.34-3.module+el8dsrv+21391+b62d2223 | | `389-ds-base` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `389-ds-base-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `389-ds-base-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `389-ds-base-legacy-tools` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `389-ds-base-legacy-tools-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `389-ds-base-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `389-ds-base-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `389-ds-base-snmp` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `389-ds-base-snmp-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `python3-lib389` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.39-3.module+el8.10.0+21535+f663b039 | | `389-ds-base` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | | `389-ds-base-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | | `389-ds-base-debugsource` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | | `389-ds-base-devel` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | | `389-ds-base-legacy-tools` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | | `389-ds-base-legacy-tools-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | | `389-ds-base-libs` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | | `389-ds-base-libs-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | | `389-ds-base-snmp` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | | `389-ds-base-snmp-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | | `python3-lib389` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.4.3.34-6.module+el8.6.0+21315+7f417418 | Products: Fedoraproject Fedora, Redhat 389 Directory Server, Redhat Directory Server, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux for Arm 64 Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Little Endian Eus, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server for Power Little Endian Update Services for Sap Solutions, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Update Services for Sap Solutions. ## How do I fix CVE-2024-1062? Apply the vendor's patch. ## Is CVE-2024-1062 being exploited? There is no known exploitation of CVE-2024-1062 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-1062 and fix it if it is affected. What it is: CVE-2024-1062 is a medium-severity memory corruption vulnerability in Fedoraproject Fedora, published on 12 Feb 2024. 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-2024-1062 in the wild and no public exploit code. Affected product: Fedoraproject Fedora. 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-2024-1062/ (Markdown: https://insights.sbomify.com/CVE-2024-1062/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1062 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1062 - OSV: https://osv.dev/vulnerability/CVE-2024-1062 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-1062/ Summaries are generated and may contain mistakes; the official description above is the record.