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

> Local attackers can access sensitive information via the FSFindFolder API due to world-readable temporary directory permissions in Mac OS X.

- **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:** No
- **Published:** 23 Mar 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-fx3c-2ghc-cxfq

## What is CVE-2011-0178?

CVE-2011-0178 is a low-severity vulnerability in Apple Mac Os X, published on 23 Mar 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The FSFindFolder API in CarbonCore in Apple Mac OS X before 10.6.7 provides a world-readable directory in response to a call with the kTemporaryFolderType flag, which allows local users to obtain potentially sensitive information by accessing this directory.

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

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

It affects 3 products.


Products: Apple Carboncore, Apple Mac Os X, Apple Mac Os X Server.

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

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

## Is CVE-2011-0178 being exploited?

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

## Other vulnerabilities in Apple Mac Os X

- [CVE-2008-2320](https://insights.sbomify.com/CVE-2008-2320/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-0178 is a low-severity vulnerability in Apple Mac Os X, published on 23 Mar 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-0178 in the wild and no public exploit code.

Affected product: Apple Mac Os X. 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-0178/ (Markdown: https://insights.sbomify.com/CVE-2011-0178/index.md)
```

## Sources

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

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