# CVE-2014-0199: Information disclosure in n/a

> Local attackers can read the reports database password from a cleartext file in the setup script, exposing sensitive credentials.

- **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:** 29 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cr4w-q8q3-vcf6

## What is CVE-2014-0199?

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

### Official description

The setup script in ovirt-engine-reports, as used in the Red Hat Enterprise Virtualization reports (rhevm-reports) package before 3.3.3, stores the reports database password in cleartext, which allows local users to obtain sensitive information by reading an unspecified file.

Weakness: CWE-310

## Which versions are affected by CVE-2014-0199?

It affects 1 product.


Products: Redhat Rhevm-Reports.

## How do I fix CVE-2014-0199?

Upgrade to a fixed version.

## Is CVE-2014-0199 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0200](https://insights.sbomify.com/CVE-2014-0200/): Information disclosure in n/a (low 2.1)
- [CVE-2014-0201](https://insights.sbomify.com/CVE-2014-0201/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0199 and fix it if it is affected.

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

## Sources

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

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