CVE-2017-15136: Input Validation
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.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat Network Satellite Server | =6.0 |
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 CVE-2017-15136?
CVE-2017-15136 is considered a moderate severity vulnerability.
How do I fix CVE-2017-15136?
To fix CVE-2017-15136, ensure that the hostnames of registered systems in Satellite 6 remain unique.
What are the consequences of CVE-2017-15136?
The exploitation of CVE-2017-15136 can lead to previously registered systems losing access to updates and security patches.
Which version of Red Hat Satellite is affected by CVE-2017-15136?
Red Hat Satellite version 6.0 is affected by CVE-2017-15136.
Who reported CVE-2017-15136?
CVE-2017-15136 was reported by Jan Hutař of Red Hat.
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/references
- agent/weakness
- agent/last-modified-date
- agent/author
- agent/description
- agent/event
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2017-15136
- agent/trending
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/tags
- agent/softwarecombine
- agent/source
- vendor/redhat
- canonical/red hat network satellite server
- version/red hat network satellite server/6.0