First published: Wed Aug 22 2018(Updated: )
It was found that Satellite 5 configured with SSL/TLS for the PostgreSQL backend failed to correctly validate X.509 server certificate host name fields. A man-in-the-middle attacker could use this flaw to spoof a PostgreSQL server using a specially crafted X.509 certificate.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Network Satellite Server | =5.0 | |
Red Hat Network Satellite Server | =5.1.1 | |
Red Hat Network Satellite Server | =5.2 | |
Red Hat Network Satellite Server | =5.3 | |
Red Hat Network Satellite Server | =5.4 | |
Red Hat Network Satellite Server | =5.4.1 | |
Red Hat Network Satellite Server | =5.5 | |
Red Hat Network Satellite Server | =5.6 | |
Red Hat Network Satellite Server | =5.7 | |
Red Hat Network Satellite Server | =5.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-7513 has been rated as a high severity vulnerability due to the potential for man-in-the-middle attacks.
To fix CVE-2017-7513, ensure that your PostgreSQL backend is configured to correctly validate X.509 server certificate host name fields.
CVE-2017-7513 affects Red Hat Satellite versions from 5.0 to 5.8.
CVE-2017-7513 can enable man-in-the-middle attacks by spoofing a PostgreSQL server with a crafted X.509 certificate.
Yes, CVE-2017-7513 specifically impacts Red Hat Satellite products configured with SSL/TLS for PostgreSQL.