# CVE-2011-1822: Information disclosure in n/a

> Local attackers can read cleartext SHA passwords from the change log in IBM Tivoli Directory Server, exposing sensitive credentials.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-37mj-2pf9-8q24

## What is CVE-2011-1822?

CVE-2011-1822 is a low-severity vulnerability in n/a, published on 21 Apr 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The LDAP_ADD implementation in IBM Tivoli Directory Server (TDS) 5.2 before 5.2.0.5-TIV-ITDS-IF0009 stores a cleartext SHA password in the change log, which might allow local users to obtain sensitive information by reading this log.

Weakness: CWE-255

## Which versions are affected by CVE-2011-1822?

It affects 1 product.


Products: Ibm Tivoli Directory Server.

## How do I fix CVE-2011-1822?

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

## Is CVE-2011-1822 being exploited?

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

What it is: CVE-2011-1822 is a low-severity vulnerability in n/a, published on 21 Apr 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1822 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-2011-1822/ (Markdown: https://insights.sbomify.com/CVE-2011-1822/index.md)
```

## Sources

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

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