# CVE-2022-2850: Null dereference in 389-ds-base > An authenticated attacker can cause a denial of service via a null pointer dereference in the Content Synchronization plugin. - **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:** 14 Oct 2022 - **Updated:** 3 Nov 2025 - **Also known as:** ALSA-2022:7133, DEBIAN-CVE-2022-2850, GHSA-6c63-4574-7p9f, MGASA-2022-0413, RHSA-2022:7087, RHSA-2022:7133, RHSA-2022:8680, RHSA-2022:8886, RHSA-2023:0479, RLSA-2022:7133, SUSE-SU-2022:3029-1, SUSE-SU-2022:3286-1, UBUNTU-CVE-2022-2850 ## What is CVE-2022-2850? CVE-2022-2850 is a medium-severity vulnerability in Debian Debian Linux, published on 14 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A flaw was found In 389-ds-base. When the Content Synchronization plugin is enabled, an authenticated user can reach a NULL pointer dereference using a specially crafted query. This flaw allows an authenticated attacker to cause a denial of service. This CVE is assigned against an incomplete fix of CVE-2021-3514. Weakness: CWE-476 (NULL Pointer Dereference) ## Which versions are affected by CVE-2022-2850? It affects 5 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `389-ds-base` | AlmaLinux:8 | All versions | 1.4.3.28-8.module_el8.6.0+3338+ebccfef1 | | `389-ds-base-devel` | AlmaLinux:8 | All versions | 1.4.3.28-8.module_el8.6.0+3338+ebccfef1 | | `389-ds-base-legacy-tools` | AlmaLinux:8 | All versions | 1.4.3.28-8.module_el8.6.0+3338+ebccfef1 | | `389-ds-base-libs` | AlmaLinux:8 | All versions | 1.4.3.28-8.module_el8.6.0+3338+ebccfef1 | | `389-ds-base-snmp` | AlmaLinux:8 | All versions | 1.4.3.28-8.module_el8.6.0+3338+ebccfef1 | | `python3-lib389` | AlmaLinux:8 | All versions | 1.4.3.28-8.module_el8.6.0+3338+ebccfef1 | | `389-ds-base` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `389-ds-base-debuginfo` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `389-ds-base-debugsource` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `389-ds-base-devel` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `389-ds-base-legacy-tools` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `389-ds-base-legacy-tools-debuginfo` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `389-ds-base-libs` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `389-ds-base-libs-debuginfo` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `389-ds-base-snmp` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `389-ds-base-snmp-debuginfo` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `cockpit-389-ds` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `python3-lib389` | Red Hat:directory_server:11.5::el8 | All versions | 0:1.4.3.29-7.module+el8dsrv+17334+74991258 | | `389-ds-base` | Red Hat:directory_server:12::el9 | All versions | 0:2.0.18-3.module+el9dsrv+17947+6e05a0b8 | | `389-ds-base-debuginfo` | Red Hat:directory_server:12::el9 | All versions | 0:2.0.18-3.module+el9dsrv+17947+6e05a0b8 | | `389-ds-base-debugsource` | Red Hat:directory_server:12::el9 | All versions | 0:2.0.18-3.module+el9dsrv+17947+6e05a0b8 | | `389-ds-base-devel` | Red Hat:directory_server:12::el9 | All versions | 0:2.0.18-3.module+el9dsrv+17947+6e05a0b8 | | `389-ds-base-libs` | Red Hat:directory_server:12::el9 | All versions | 0:2.0.18-3.module+el9dsrv+17947+6e05a0b8 | | `389-ds-base-libs-debuginfo` | Red Hat:directory_server:12::el9 | All versions | 0:2.0.18-3.module+el9dsrv+17947+6e05a0b8 | | `389-ds-base-snmp` | Red Hat:directory_server:12::el9 | All versions | 0:2.0.18-3.module+el9dsrv+17947+6e05a0b8 | | `389-ds-base-snmp-debuginfo` | Red Hat:directory_server:12::el9 | All versions | 0:2.0.18-3.module+el9dsrv+17947+6e05a0b8 | | `cockpit-389-ds` | Red Hat:directory_server:12::el9 | All versions | 0:2.0.18-3.module+el9dsrv+17947+6e05a0b8 | | `python3-lib389` | Red Hat:directory_server:12::el9 | All versions | 0:2.0.18-3.module+el9dsrv+17947+6e05a0b8 | | `389-ds-base` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base-snmp` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base-snmp` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.10.2-17.el7_9 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.10.2-17.el7_9 | Products: Debian Debian Linux, Fedoraproject Fedora, Port389 389-Ds-Base, Redhat Directory Server, Redhat Enterprise Linux. ## How do I fix CVE-2022-2850? Apply the vendor's patch. ## Is CVE-2022-2850 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2850 exists. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-2850 and fix it if it is affected. What it is: CVE-2022-2850 is a medium-severity vulnerability in Debian Debian Linux, published on 14 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2850 exists. Affected product: Debian Debian Linux. 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-2022-2850/ (Markdown: https://insights.sbomify.com/CVE-2022-2850/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2850 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2850 - OSV: https://osv.dev/vulnerability/CVE-2022-2850 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-2850/ Summaries are generated and may contain mistakes; the official description above is the record.