5: Failure to verify DB hostname against hostname in certificate in PostgreSQL through SSL configuration
Published Aug 22, 2018
5.4
MEDIUMCVSS 3.0
EPSS 0.48%
Description
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.
Affected products
-
- Version 5StatusaffectedConstraints-
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | Red Hat Satellite | n/a |
|
- 5.0
- 5.1.1
- 5.2
- 5.3
- 5.4
- 5.4.1
- 5.5
- 5.6
- 5.7
- 5.8
No data.
Red Hat Satellite 5
security
Affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Satellite 5 | security | Affected | n/a |
No package ranges for this CVE.
Remediation
Red Hat 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/.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
AV:N/AC:M/Au:N/C:P/I:P/A:N
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
Percentile over time
- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
Table of values (9 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 0.48% (0.00484) | 39.41th | v5 (v2026.06.15) |
| Sep 20, 2026 | 0.48% (0.00484) | 40.80th | v5 (v2026.06.15) |
| Jul 20, 2024 | 0.07% (0.00066) | 29.63th | v3 (v2023.03.01) |
| Jun 14, 2024 | 0.07% (0.00065) | 28.67th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.07% (0.00065) | 26.64th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.89% (0.00885) | 27.89th | v2 (v2022.01.01) |
| Feb 4, 2022 | 0.89% (0.00885) | 10.50th | v2 (v2022.01.01) |
| Feb 3, 2022 | 0.42% (0.00416) | 10.04th | v5 (v2026.06.15) |
| Apr 14, 2021 | 0.42% (0.00416) | 0.00th | v1 |
References (6)
- https://access.redhat.com/security/cve/CVE-2017-7513 Vendor Advisory
- https://access.redhat.com/security/cve/cve-2017-7513 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1458057 Issue Tracking
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7513 x_refsource_CONFIRMIssue TrackingVendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2017-7513
- https://www.cve.org/CVERecord?id=CVE-2017-7513
| Link | Providers | Tags |
|---|---|---|
| https://access.redhat.com/security/cve/CVE-2017-7513 | Vendor Advisory | |
| https://access.redhat.com/security/cve/cve-2017-7513 | Vendor Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1458057 | Issue Tracking | |
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7513 | x_refsource_CONFIRMIssue TrackingVendor Advisory | |
| https://nvd.nist.gov/vuln/detail/CVE-2017-7513 | ||
| https://www.cve.org/CVERecord?id=CVE-2017-7513 |
Change history (0)
No recorded changes yet.