REDHAT-BUG-1540343
First published: Tue Jan 30 2018(Updated: )
Jan Hutař of Red Hat reports: When registering and activating a new system with Satellite 6 if the new systems hostname is then reset to the hostname of a previously registered system the previously registered system will lose access to updates including security updates.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat Satellite |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of REDHAT-BUG-1540343?
The severity of REDHAT-BUG-1540343 is considered moderate due to potential disruption in accessing updates.
How do I fix REDHAT-BUG-1540343?
To fix REDHAT-BUG-1540343, avoid reusing hostnames from previously registered systems.
What systems are affected by REDHAT-BUG-1540343?
REDHAT-BUG-1540343 affects Red Hat Satellite 6 when registering new systems.
What impact does REDHAT-BUG-1540343 have on registered systems?
The impact of REDHAT-BUG-1540343 is that a previously registered system will lose access to updates if its hostname is reused.
Is there a workaround for REDHAT-BUG-1540343?
A viable workaround for REDHAT-BUG-1540343 is to always ensure unique hostnames for all registered systems.
- agent/references
- agent/last-modified-date
- agent/first-publish-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2017-15136
- agent/severity
- agent/type
- agent/description
- agent/event
- agent/trending
- agent/source
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/red hat
- canonical/red hat satellite