# CVE-2011-1500: Information disclosure in n/a

> Local attackers can read Pandora credentials from the Pithos configuration file due to improper permission restrictions.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-1500, GHSA-p72p-3m8j-v5mg

## What is CVE-2011-1500?

CVE-2011-1500 is a low-severity vulnerability in n/a, published on 13 Apr 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PreferencesPithosDialog.py in Pithos 0.3.7 does not properly restrict permissions for the .config/pithos.ini file in a user's home directory, which allows local users to obtain Pandora credentials by reading this file.

Weakness: CWE-264

## Which versions are affected by CVE-2011-1500?

It affects 1 product.


Products: Kevinmehall Pithos.

## How do I fix CVE-2011-1500?

Apply the vendor's patch.

## Is CVE-2011-1500 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1500 and fix it if it is affected.

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

## Sources

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

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