SatelliteApplication · Redhat
CVE-2020-14371
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA credential leak vulnerability was found in Red Hat Satellite. This flaw exposes the compute resources credentials through VMs that are running on these resources in Satellite.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceRed Hat Satellite contains a credential leak vulnerability that exposes compute resource credentials to virtual machines running on those resources. An attacker with access to a VM could potentially retrieve the underlying compute resource credentials through this exposure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SatelliteApplication
= 6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Red Hat Satellite installation and versionCheck if Red Hat Satellite is installed on the system and determine the exact version by querying the Satellite server or checking installed packages. Common methods include checking the Satellite UI version page, running 'satellite --version' from the command line, or querying the RPM package: rpm -q foremanAffected if The installed version is Red Hat Satellite 6.0
-
Verify compute resources are configuredLog in to the Red Hat Satellite web UI and navigate to Infrastructure > Compute Resources, or use the Satellite API to list compute resources. Check if any compute resources (such as Red Hat Virtualization, VMware, OpenStack, or other cloud providers) are definedAffected if One or more compute resources are configured and associated with the Satellite installation
-
Check for virtual machines on compute resourcesNavigate to Hosts > All Hosts in the Satellite UI, or query the API to list all virtual machines. Identify which compute resource each VM is hosted onAffected if Any virtual machines are running on the configured compute resources
-
Assess credential exposure riskReview the compute resource configurations to confirm that credentials for the underlying compute infrastructure are stored within Satellite. In the Compute Resources settings, verify that authentication credentials are saved (not entered on-demand)Affected if Compute resource credentials are stored persistently in Satellite and VMs exist on those resources
A user is affected if they run Red Hat Satellite version 6.0 with compute resources configured and have virtual machines running on those compute resources, as the stored credentials could be exposed to VM users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the appropriate Red Hat Satellite security update or patch for CVE-2020-14371. Review and rotate any credentials that may have been exposed through this vulnerability.
Fix this in Satellite
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14371 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data