# CVE-2015-0257: Information disclosure in n/a

> Local users can read sensitive files from shared directories due to weak permissions in RHEV Manager.

- **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:** 1 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7944-mp99-q983

## What is CVE-2015-0257?

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

### Official description

Red Hat Enterprise Virtualization (RHEV) Manager before 3.5.1 uses weak permissions on the directories shared by the ovirt-engine-dwhd service and a plugin during service startup, which allows local users to obtain sensitive information by reading files in the directory.

Weakness: CWE-264

## Which versions are affected by CVE-2015-0257?

It affects 1 product.


Products: Redhat Enterprise Virtualization Manager.

## How do I fix CVE-2015-0257?

Upgrade to a fixed version.

## Is CVE-2015-0257 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7544](https://insights.sbomify.com/CVE-2015-7544/): Command injection in n/a (critical 9.1)
- [CVE-2015-0237](https://insights.sbomify.com/CVE-2015-0237/): Missing authorization in n/a (medium 6.8)
- [CVE-2012-0861](https://insights.sbomify.com/CVE-2012-0861/): Security feature bypass in n/a (medium 6.8)
- [CVE-2010-2793](https://insights.sbomify.com/CVE-2010-2793/): Race condition in n/a (medium 6.8)
- [CVE-2014-3573](https://insights.sbomify.com/CVE-2014-3573/): XML external entity in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0257 and fix it if it is affected.

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

## Sources

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

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