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

> Local attackers can read sensitive mail data due to world-readable permissions in the Evolution mail client's configuration directory.

- **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:** 14 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1631, GHSA-q8vh-phfc-qrw2

## What is CVE-2009-1631?

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

### Official description

The Mailer component in Evolution 2.26.1 and earlier uses world-readable permissions for the .evolution directory, and certain directories and files under .evolution/ related to local mail, which allows local users to obtain sensitive information by reading these files.

Weakness: CWE-264

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

It affects 1 product.


Products: Gnome Evolution.

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

Upgrade to a fixed version.

## Is CVE-2009-1631 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12422](https://insights.sbomify.com/CVE-2018-12422/): Memory corruption in n/a (critical 9.8)
- [CVE-2008-1109](https://insights.sbomify.com/CVE-2008-1109/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-3721](https://insights.sbomify.com/CVE-2009-3721/): Path traversal in ytnef (high 7.8)
- [CVE-2008-1108](https://insights.sbomify.com/CVE-2008-1108/): Memory corruption in n/a (high 7.6)
- [CVE-2013-4166](https://insights.sbomify.com/CVE-2013-4166/): Information disclosure in Evolution (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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