dbcve.org
EsxiOperating system · VMware

CVE-2010-0211

CRITICAL · 9.8 CVSS v3.1 Published 2010-07-28
Fix available
A fix is available. Upgrade to 10.6.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EsxiOperating system
Affected:= 4.0= 4.1
OpenldapApplication
Affected:= 2.4.22
OpensuseOperating system
Affected:= 11.0
Mac Os XOperating system
Affected:>= 10.6.0, < 10.6.5
Mac Os X ServerOperating system
Affected:>= 10.6.0, < 10.6.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.6.5 or later
Fixed in 10.6.5
Vendor patch www.securityfocus.com →
Recommended fix High confidence

OpenLDAP 2.4.23 or later (for standalone OpenLDAP); VMware ESXi 4.0/4.1 vendor patches; Mac OS X 10.6.5 or later

  1. 1. Identify the OpenLDAP installation version by running 'slapd -V' or checking the package manager
  2. 2. For systems running OpenLDAP 2.4.22, upgrade to OpenLDAP 2.4.23 or later (e.g., 2.4.24) which contains the fix for the smr_normalize return value check
  3. 3. For VMware ESXi 4.0/4.1, apply the respective VMware security patches for this CVE
  4. 4. For Mac OS X 10.6.0-10.6.4, upgrade to Mac OS X 10.6.5 or later which includes the fixed OpenLDAP version
  5. 5. For OpenSUSE 11.0, apply the openSUSE security update for this issue
  6. 6. After upgrading, restart the OpenLDAP service (slapd) to load the fixed library
  7. 7. Verify the fix by testing LDAP modrdn operations with both valid and invalid UTF-8 input
Caveat Upgrading OpenLDAP may require configuration review; ensure custom schemas and ACLs are compatible with the new version

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0211 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0211 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data