SatelliteApplication · Redhat
CVE-2020-14335
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, which allows a privileged attacker to read OMAPI secrets through the ISC DHCP of Smart-Proxy. This flaw allows an attacker to gain control of DHCP records from the network. The highest threat from this vulnerability is to system availability.
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 confidenceA flaw in Red Hat Satellite allows a privileged attacker to read OMAPI secrets through the ISC DHCP service of Smart-Proxy. By exploiting this, an attacker can obtain credentials that grant control over DHCP records on the network, enabling manipulation of network service availability.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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 versionRun 'rpm -q tfm-redhat-satellite' or check the Satellite web UI under Admin > Settings > General to confirm the installed versionAffected if Version is 6.0 exactly (the only affected version listed)
-
Verify Smart-Proxy DHCP module is enabledCheck Smart-Proxy configuration files (typically under /etc/foreman-proxy/settings.yml or /etc/foreman-proxy/modules.d/) and confirm the DHCP module is loaded and activeAffected if Smart-Proxy with ISC DHCP service is enabled and running
-
Inspect OMAPI configuration in DHCPExamine the DHCP server configuration files (usually in /etc/dhcp/ or via 'satellite-proxy' CLI) for OMAPI settings - look for 'omapi-port' or 'key' declarations in the dhcpd.confAffected if OMAPI is configured with secrets/keys that could be exposed
-
Check OMAPI secret file permissions and contentLocate OMAPI key files (commonly in /etc/dhcp/dhcpd.keys or similar paths under /var/lib/tftpboot/boot/) and verify file ownership and read permissions - check if unprivileged users can read these filesAffected if OMAPI secret file exists and is readable by users other than the dhcp service account or root
User is affected if running Red Hat Satellite 6.0 with Smart-Proxy DHCP/OMAPI enabled, where OMAPI secrets are accessible to privileged users or have improper file permissions.
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 dataRestrict privileged access to Red Hat Satellite and Smart-Proxy components, rotate OMAPI secrets immediately, and apply available Red Hat patches. Review DHCP configuration for unauthorized changes.
Fix this in Satellite
Scoped from the published advisory
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14335 — 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-14335 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