Bug 1458057 (CVE-2017-7513) - CVE-2017-7513 SAT 5: Failure to verify DB hostname against hostname in certificate in PostgreSQL through SSL configuration
Summary: CVE-2017-7513 SAT 5: Failure to verify DB hostname against hostname in certif...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2017-7513
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1451656
Blocks: 1452193
TreeView+ depends on / blocked
 
Reported: 2017-06-01 22:12 UTC by Kurt Seifried
Modified: 2021-08-18 09:04 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2017-07-25 21:32:07 UTC
Embargoed:

Attachments (Terms of Use)

Description Kurt Seifried 2017-06-01 22:12:35 UTC 
Lukáš Hellebrandt of Red Hat reports:

When running Satellite with external PostgreSQL backend, it is possible to secure the Satellite <-> DB server with SSL/TLS.
However, Satellite's Java part (contrary to backend), while it does verify the DB host's certificate against CA cert, does NOT verify the DB host's hostname against the one in its certificate.
Comment 3 Kurt Seifried 2017-07-25 21:31:30 UTC 
Statement:

Red Hat Satellite 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.
Note You need to log in before you can comment on or make changes to this bug.