# CVE-2021-3514: Null dereference in 389-ds-base > An authenticated attacker can crash the 389-ds-base server via a NULL pointer dereference in the sync_repl client. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 May 2021 - **Updated:** 3 Aug 2024 - **Also known as:** DEBIAN-CVE-2021-3514, GHSA-4mjm-c95j-8748, RHSA-2021:2595, RHSA-2021:2796, RLSA-2021:2595, SUSE-SU-2021:1878-1, UBUNTU-CVE-2021-3514, openSUSE-SU-2021:0868-1 ## What is CVE-2021-3514? CVE-2021-3514 is a medium-severity vulnerability in 389-ds-base, published on 28 May 2021. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description When using a sync_repl client in 389-ds-base, an authenticated attacker can cause a NULL pointer dereference using a specially crafted query, causing a crash. Weakness: CWE-476 (NULL Pointer Dereference) ## Which versions are affected by CVE-2021-3514? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `389-ds-base` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `389-ds-base-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `389-ds-base-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `389-ds-base-legacy-tools` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `389-ds-base-legacy-tools-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `389-ds-base-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `389-ds-base-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `389-ds-base-snmp` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `389-ds-base-snmp-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `python3-lib389` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.3.16-16.module+el8.4.0+11446+fc96bc48 | | `389-ds-base` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `389-ds-base-debuginfo` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `389-ds-base-debugsource` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `389-ds-base-devel` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `389-ds-base-legacy-tools` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `389-ds-base-legacy-tools-debuginfo` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `389-ds-base-libs` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `389-ds-base-libs-debuginfo` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `389-ds-base-snmp` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `389-ds-base-snmp-debuginfo` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `python3-lib389` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.4.2.4-14.module+el8.2.0+11017+0eb5711a | | `389-ds-base` | Rocky Linux:8 | All versions | 0:1.4.3.16-16.module+el8.4.0+596+159889e5 | | `389-ds` | SUSE:Linux Enterprise Module for Server Applications 15 SP2 | All versions | 1.4.3.23~git0.f53d0132b-3.15.1 | | `389-ds` | openSUSE:Leap 15.2 | All versions | 1.4.3.23~git0.f53d0132b-lp152.2.15.1 | Products: Redhat 389 Directory Server. ## How do I fix CVE-2021-3514? Apply the vendor's patch. ## Is CVE-2021-3514 being exploited? There is no known exploitation of CVE-2021-3514 in the wild and no public exploit code. ## Other vulnerabilities in 389-ds-base - [CVE-2026-11770](https://insights.sbomify.com/CVE-2026-11770/): 389-ds-base: 389-ds-base: pre-auth ldap filter injection in cleanallruv status check (high 7.5) - [CVE-2026-15722](https://insights.sbomify.com/CVE-2026-15722/): Memory corruption in Red Hat Directory Server 11.5 E4S for RHEL 8 (high 7.5) - [CVE-2026-9064](https://insights.sbomify.com/CVE-2026-9064/): Denial of service in Red Hat Directory Server 11.5 E4S for RHEL 8 (high 7.5) - [CVE-2010-2222](https://insights.sbomify.com/CVE-2010-2222/): Null dereference in Red Hat Directory Server (high 7.5) - [CVE-2026-11611](https://insights.sbomify.com/CVE-2026-11611/): 389-ds-base: 389-ds-base: content sync plugin unbounded queue growth and race conditions (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-3514 and fix it if it is affected. What it is: CVE-2021-3514 is a medium-severity vulnerability in 389-ds-base, published on 28 May 2021. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2021-3514 in the wild and no public exploit code. Affected product: 389-ds-base. 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-2021-3514/ (Markdown: https://insights.sbomify.com/CVE-2021-3514/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-3514 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-3514 - OSV: https://osv.dev/vulnerability/CVE-2021-3514 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-3514/ Summaries are generated and may contain mistakes; the official description above is the record.