# CVE-2010-4217: Use after free in n/a

> Remote attackers can crash the IBM Tivoli Directory Server daemon via a specific unbind request during a search operation.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Nov 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-272m-2g9c-jj9w

## What is CVE-2010-4217?

CVE-2010-4217 is a medium-severity use after free vulnerability in n/a, published on 9 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use-after-free vulnerability in the proxy server in IBM Tivoli Directory Server (TDS) 6.0.0.x before 6.0.0.8-TIV-ITDS-IF0007 and 6.1.x before 6.1.0-TIV-ITDS-FP0005 allows remote attackers to cause a denial of service (daemon crash) via an unbind request that occurs during a certain search operation.

Weakness: CWE-399

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

It affects 1 product.


Products: Ibm Tivoli Directory Server.

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

No fix has been published for CVE-2010-4217 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-4217 being exploited?

There is no known exploitation of CVE-2010-4217 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2011-1206](https://insights.sbomify.com/CVE-2011-1206/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-1975](https://insights.sbomify.com/CVE-2015-1975/): Command injection in n/a (high 7.8)
- [CVE-2009-3089](https://insights.sbomify.com/CVE-2009-3089/): Null dereference in n/a (high 7.8)
- [CVE-2009-3088](https://insights.sbomify.com/CVE-2009-3088/): Memory corruption in n/a (high 7.5)
- [CVE-2007-6742](https://insights.sbomify.com/CVE-2007-6742/): Denial of service in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-4217 is a medium-severity use after free vulnerability in n/a, published on 9 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-4217 in the wild and no public exploit code.

Affected product: n/a. 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-4217/ (Markdown: https://insights.sbomify.com/CVE-2010-4217/index.md)
```

## Sources

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

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