# CVE-2022-25805: Information disclosure in n/a

> An attacker intercepting traffic can steal cleartext LDAP credentials from IGEL UMS, potentially compromising directory access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 9 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9j28-82fg-7vjq

## What is CVE-2022-25805?

CVE-2022-25805 is a medium-severity vulnerability in n/a, published on 9 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in the IGEL Universal Management Suite (UMS) 6.07.100. The transmission of cleartext LDAP bind credentials by the cmd_mgt_load_mgt_tree command allows an attacker (who can intercept or inspect traffic between an authenticated UMS client and server) to compromise those LDAP bind credentials.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2022-25805?

It affects 1 product.


Products: Igel Universal Management Suite.

## How do I fix CVE-2022-25805?

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

## Is CVE-2022-25805 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-25806](https://insights.sbomify.com/CVE-2022-25806/): Hardcoded credentials in n/a (high 8.8)
- [CVE-2022-25804](https://insights.sbomify.com/CVE-2022-25804/): Information disclosure in n/a (medium 5.5)
- [CVE-2022-25807](https://insights.sbomify.com/CVE-2022-25807/): Hardcoded credentials in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25805 and fix it if it is affected.

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

## Sources

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

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