# CVE-2010-2241: Information disclosure in n/a

> Local attackers can read world-readable cache files to steal administrative passwords, leading to privilege escalation in Red Hat Directory Server.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g8wm-c6h5-35rm, RHSA-2010:0590

## What is CVE-2010-2241?

CVE-2010-2241 is a low-severity vulnerability in n/a, published on 17 Aug 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The (1) setup-ds.pl and (2) setup-ds-admin.pl setup scripts for Red Hat Directory Server 8 before 8.2 use world-readable permissions when creating cache files, which allows local users to obtain sensitive information including passwords for Directory and Administration Server administrative accounts.

Weakness: CWE-264

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `idm-console-framework` | Red Hat:directory_server:8::el5 | All versions | 0:1.1.5-1.el5idm |
| `jss` | Red Hat:directory_server:8::el5 | All versions | 0:4.2.6-6.el5idm |
| `jss-debuginfo` | Red Hat:directory_server:8::el5 | All versions | 0:4.2.6-6.el5idm |
| `redhat-admin-console` | Red Hat:directory_server:8::el5 | All versions | 0:8.2.0-2.el5dsrv |
| `redhat-ds` | Red Hat:directory_server:8::el5 | All versions | 0:8.2.0-2.el5dsrv |
| `redhat-ds-admin` | Red Hat:directory_server:8::el5 | All versions | 0:8.2.0-3.el5dsrv |
| `redhat-ds-admin-debuginfo` | Red Hat:directory_server:8::el5 | All versions | 0:8.2.0-3.el5dsrv |
| `redhat-ds-base` | Red Hat:directory_server:8::el5 | All versions | 0:8.2.0-13.el5dsrv |
| `redhat-ds-base-debuginfo` | Red Hat:directory_server:8::el5 | All versions | 0:8.2.0-13.el5dsrv |
| `redhat-ds-base-devel` | Red Hat:directory_server:8::el5 | All versions | 0:8.2.0-13.el5dsrv |
| `redhat-ds-console` | Red Hat:directory_server:8::el5 | All versions | 0:8.2.0-4.el5dsrv |
| `redhat-idm-console` | Red Hat:directory_server:8::el5 | All versions | 0:1.0.2-1.el5idm |
| `redhat-idm-console-debuginfo` | Red Hat:directory_server:8::el5 | All versions | 0:1.0.2-1.el5idm |

Products: Redhat Directory Server.

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

Upgrade to a fixed version.

## Is CVE-2010-2241 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2928](https://insights.sbomify.com/CVE-2008-2928/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-0892](https://insights.sbomify.com/CVE-2008-0892/): Command injection in n/a (critical 9.0)
- [CVE-2008-1677](https://insights.sbomify.com/CVE-2008-1677/): Memory corruption in n/a (high 7.5)
- [CVE-2008-0893](https://insights.sbomify.com/CVE-2008-0893/): Missing authorization in n/a (high 7.5)
- [CVE-2008-0890](https://insights.sbomify.com/CVE-2008-0890/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2241 is a low-severity vulnerability in n/a, published on 17 Aug 2010. 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-2010-2241 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-2241/ (Markdown: https://insights.sbomify.com/CVE-2010-2241/index.md)
```

## Sources

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

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