# CVE-2009-1296: Information disclosure in n/a

> Local attackers with root privileges can read installation logs to obtain eCryptfs mount passphrases, potentially accessing encrypted filesystems.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1296, GHSA-wp7j-cfx2-2rxm

## What is CVE-2009-1296?

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

### Official description

The eCryptfs support utilities (ecryptfs-utils) 73-0ubuntu6.1 on Ubuntu 9.04 stores the mount passphrase in installation logs, which might allow local users to obtain access to the filesystem by reading the log files from disk.  NOTE: the log files are only readable by root.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Ubuntu 73-Oubuntu, Ubuntu Ubuntu.

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

Apply the vendor's patch.

## Is CVE-2009-1296 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1296 and fix it if it is affected.

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

## Sources

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

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