SatelliteApplication · Redhat
CVE-2020-10716
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 flaw was found in Red Hat Satellite's Job Invocation, where the "User Input" entry was not properly restricted to the view. This flaw allows a malicious Satellite user to scan through the Job Invocation, with the ability to search for passwords and other sensitive data. This flaw affects tfm-rubygem-foreman_ansible versions before 4.0.3.4.
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 · high confidenceIn foreman_ansible plugin versions before 4.0.3.4, the Job Invocation 'User Input' feature did not properly restrict sensitive data (passwords, secrets) from being viewed. A malicious authenticated Satellite user could enumerate Job Invocations and extract plaintext passwords or other sensitive data that should have been hidden or redacted from the UI.
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.7
Satellite CapsuleApplication
= 6.7
Foreman AnsibleApplication
< 4.0.3.4CVSS 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 foreman_ansible plugin installationQuery the plugin list or installed packages to determine if the foreman_ansible plugin is present in the Satellite or Foreman installationAffected if The foreman_ansible plugin is installed and no version is returned or the returned version is below 4.0.3.4
-
Determine foreman_ansible versionCheck the installed version of tfm-rubygem-foreman_ansible or foreman_ansible using the package manager or the Foreman About pageAffected if The installed version is earlier than 4.0.3.4
-
Verify Red Hat Satellite versionCheck the installed version of Red Hat Satellite or Capsule using 'satellite-installer --version' or the About pageAffected if The Satellite or Capsule version is 6.7 and the foreman_ansible plugin version cannot be determined or is below 4.0.3.4
-
Inspect Job Invocation recordsQuery the Job Invocations database or UI for records that contain user input fields, particularly those with names suggesting sensitive data such as passwords, secrets, or credentialsAffected if Job Invocation records with user input fields exist in the system and the foreman_ansible version is vulnerable
A user is affected if they have foreman_ansible plugin installed with a version earlier than 4.0.3.4 (or are running Satellite 6.7 with an unknown or vulnerable foreman_ansible version) and have Job Invocations that contain sensitive user input data that could be enumerated.
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 data4.0.3.4
Upgrade tfm-rubygem-foreman_ansible to version 4.0.3.4 or later which implements proper view restrictions on sensitive user input fields.
Fix this in Satellite
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10716 — 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-10716 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