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

> Local attackers can determine the existence of arbitrary files on the system via the pkexec utility in PolicyKit.

- **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:** No
- **Published:** 6 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mjg5-5qf3-5mwg

## What is CVE-2010-0750?

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

### Official description

pkexec.c in pkexec in libpolkit in PolicyKit 0.96 allows local users to determine the existence of arbitrary files via the argument.

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

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

It affects 1 product.


Products: Freedesktop Policykit.

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

No fix has been published for CVE-2010-0750 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-0750 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1658](https://insights.sbomify.com/CVE-2008-1658/): Memory corruption in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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