# CVE-2009-5073: Denial of service in n/a

> Authenticated users can cause a denial of service in IBM Tivoli Directory Server by creating a nested group with a circular parent reference.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7x46-w25m-c3rr

## What is CVE-2009-5073?

CVE-2009-5073 is a medium-severity denial of service vulnerability in n/a, published on 21 Apr 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Tivoli Directory Server (TDS) 6.0 before 6.0.0.59 (aka 6.0.0.8-TIV-ITDS-IF0001) allows remote authenticated users to cause a denial of service (infinite loop and daemon hang) by adding a nested group that contains the Distinguished Name (DN) of its parent entry.

Weakness: CWE-399

## Which versions are affected by CVE-2009-5073?

It affects 1 product.


Products: Ibm Tivoli Directory Server.

## How do I fix CVE-2009-5073?

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

## Is CVE-2009-5073 being exploited?

There is no known exploitation of CVE-2009-5073 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-2009-5073 and fix it if it is affected.

What it is: CVE-2009-5073 is a medium-severity denial of service vulnerability in n/a, published on 21 Apr 2011. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-5073 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-2009-5073/ (Markdown: https://insights.sbomify.com/CVE-2009-5073/index.md)
```

## Sources

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

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