# CVE-2010-0211: Null dereference in n/a

> Remote attackers can cause a denial of service or potentially execute arbitrary code in OpenLDAP by sending malformed UTF-8 sequences in modrdn calls.

- **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:** 27 Jul 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-0211, GHSA-m9h3-f3g9-fqrf

## What is CVE-2010-0211?

CVE-2010-0211 is a critical vulnerability in Apple Mac Os X, published on 27 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The slap_modrdn2mods function in modrdn.c in OpenLDAP 2.4.22 does not check the return value of a call to the smr_normalize function, which allows remote attackers to cause a denial of service (segmentation fault) and possibly execute arbitrary code via a modrdn call with an RDN string containing invalid UTF-8 sequences, which triggers a free of an invalid, uninitialized pointer in the slap_mods_free function, as demonstrated using the Codenomicon LDAPv3 test suite.

Weakness: CWE-252 (Unchecked Return Value)

## Which versions are affected by CVE-2010-0211?

It affects 5 products.


Products: Apple Mac Os X, Apple Mac Os X Server, Openldap Openldap, Opensuse Opensuse, Vmware Esxi.

## How do I fix CVE-2010-0211?

Apply the vendor's patch.

## Is CVE-2010-0211 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0211 exists.

Public exploit code:

- OpenLDAP 2.4.22 - 'modrdn' Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in Apple Mac Os X

- [CVE-2014-7169](https://insights.sbomify.com/CVE-2014-7169/): GNU Bourne-Again Shell (Bash) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2014-6271](https://insights.sbomify.com/CVE-2014-6271/): GNU Bourne-Again Shell (Bash) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-1823](https://insights.sbomify.com/CVE-2012-1823/): PHP-CGI Query String Parameter (critical 9.8, exploited in the wild)
- [CVE-2021-30713](https://insights.sbomify.com/CVE-2021-30713/): Apple macOS Unspecified (high 7.8, exploited in the wild)
- [CVE-2019-8526](https://insights.sbomify.com/CVE-2019-8526/): Apple macOS Use-After-Free (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0211 and fix it if it is affected.

What it is: CVE-2010-0211 is a critical vulnerability in Apple Mac Os X, published on 27 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0211 exists.

Affected product: Apple Mac Os X. 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-2010-0211/ (Markdown: https://insights.sbomify.com/CVE-2010-0211/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-0211
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-0211
- OSV: https://osv.dev/vulnerability/CVE-2010-0211

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-0211/
Summaries are generated and may contain mistakes; the official description above is the record.