# CVE-2014-3692: Hardcoded credentials in n/a

> Remote attackers can gain root privileges in Red Hat CloudForms due to a default password used for new images.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c5gm-gj7m-3h35

## What is CVE-2014-3692?

CVE-2014-3692 is a critical vulnerability in n/a, published on 16 Jan 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The customization template in Red Hat CloudForms 3.1 Management Engine (CFME) 5.3 uses a default password for the root account when a password is not specified for a new image, which allows remote attackers to gain privileges.

Weakness: CWE-255

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

It affects 1 product.


Products: Redhat Cloudforms 3.1 Management Engine.

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

Apply the vendor's patch.

## Is CVE-2014-3692 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-7814](https://insights.sbomify.com/CVE-2014-7814/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3692 is a critical vulnerability in n/a, published on 16 Jan 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3692 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-3692/ (Markdown: https://insights.sbomify.com/CVE-2014-3692/index.md)
```

## Sources

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

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