CVE-2017-7513

UnknownEPSS 0.48%

Last modified

CVE-2017-7513 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.48% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.48%

38.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
RedhatSatellite5.0
RedhatSatellite5.1.1
RedhatSatellite5.2
RedhatSatellite5.3
RedhatSatellite5.4
RedhatSatellite5.4.1
RedhatSatellite5.5
RedhatSatellite5.6
RedhatSatellite5.7
RedhatSatellite5.8

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-7513?
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.
How severe is CVE-2017-7513?
Severity scoring for CVE-2017-7513 is pending analysis. The EPSS model estimates a 0.48% probability of exploitation in the next 30 days.
How do I fix CVE-2017-7513?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-7513?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST