# CVE-2020-14334: Information disclosure in Red Hat Satellite

> A privileged attacker can read cache files to obtain credentials and gain complete control of the Red Hat Satellite instance.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 31 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cjmx-h785-pr4r, RHSA-2020:4127

## What is CVE-2020-14334?

CVE-2020-14334 is a high-severity vulnerability in Redhat Satellite, published on 31 Jul 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in Red Hat Satellite 6 which allows privileged attacker to read cache files. These cache credentials could help attacker to gain complete control of the Satellite instance.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2020-14334?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `foreman` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-cli` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-debug` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-ec2` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-gce` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-journald` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-libvirt` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-openstack` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-ovirt` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-postgresql` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-rackspace` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-telemetry` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-vmware` | Red Hat:satellite:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman` | Red Hat:satellite_capsule:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |
| `foreman-debug` | Red Hat:satellite_capsule:6.7::el7 | All versions | 0:1.24.1.28-3.el7sat |

Products: Redhat Satellite.

## How do I fix CVE-2020-14334?

Apply the vendor's patch.

## Is CVE-2020-14334 being exploited?

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

## Other vulnerabilities in Redhat Satellite

- [CVE-2024-7012](https://insights.sbomify.com/CVE-2024-7012/): Puppet-foreman: an authentication bypass vulnerability exists in foreman (critical 9.8)
- [CVE-2024-7923](https://insights.sbomify.com/CVE-2024-7923/): Puppet-pulpcore: an authentication bypass vulnerability exists in pulpcore (critical 9.8)
- [CVE-2026-96659](https://insights.sbomify.com/CVE-2026-96659/): Foreman: excessive permissions for viewer role on preview (critical 9.1)
- [CVE-2023-0118](https://insights.sbomify.com/CVE-2023-0118/): Foreman: arbitrary code execution through templates (critical 9.1)
- [CVE-2008-2369](https://insights.sbomify.com/CVE-2008-2369/): Hardcoded credentials in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14334 and fix it if it is affected.

What it is: CVE-2020-14334 is a high-severity vulnerability in Redhat Satellite, published on 31 Jul 2020. 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-2020-14334 in the wild and no public exploit code.

Affected product: Redhat Satellite. 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-2020-14334/ (Markdown: https://insights.sbomify.com/CVE-2020-14334/index.md)
```

## Sources

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

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