# CVE-2008-2368: Information disclosure in n/a

> Local attackers can read cleartext passwords from debug logs due to weak file permissions in Red Hat Certificate System.

- **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:** 20 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hj7g-ch5r-67hc

## What is CVE-2008-2368?

CVE-2008-2368 is a low-severity vulnerability in n/a, published on 20 Jan 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Red Hat Certificate System 7.2 stores passwords in cleartext in the UserDirEnrollment log, the RA wizard installer log, and unspecified other debug log files, and uses weak permissions for these files, which allows local users to discover passwords by reading the files.

Weakness: CWE-255

## Which versions are affected by CVE-2008-2368?

It affects 1 product.


Products: Redhat Certificate System.

## How do I fix CVE-2008-2368?

Apply the vendor's patch.

## Is CVE-2008-2368 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-1886](https://insights.sbomify.com/CVE-2013-1886/): Other in n/a (high 7.5)
- [CVE-2009-0588](https://insights.sbomify.com/CVE-2009-0588/): Missing authorization in n/a (medium 6.5)
- [CVE-2010-3868](https://insights.sbomify.com/CVE-2010-3868/): Missing authorization in n/a (medium 5.8)
- [CVE-2012-3367](https://insights.sbomify.com/CVE-2012-3367/): Missing authorization in n/a (medium 5.5)
- [CVE-2013-1885](https://insights.sbomify.com/CVE-2013-1885/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2368 and fix it if it is affected.

What it is: CVE-2008-2368 is a low-severity vulnerability in n/a, published on 20 Jan 2009. 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-2008-2368 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-2008-2368/ (Markdown: https://insights.sbomify.com/CVE-2008-2368/index.md)
```

## Sources

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

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