Public Date:
1622225: CVE-2018-10936 PostgreSQL: Postgres JDBC driver does not perform host name validation by default
A weakness was found in postgresql-jdbc. It was possible to provide an SSL Factory and not check the host name if a host name verifier was not provided to the driver. This could lead to a condition where a man-in-the-middle attacker could masquerade as a trusted server by providing a certificate for the wrong host, as long as it was signed by a trusted CA.

Find out more about CVE-2018-10936 from the MITRE CVE dictionary dictionary and NIST NVD.

CVSS v3 metrics

NOTE: The following CVSS v3 metrics and score provided are preliminary and subject to review.

CVSS3 Base Score 8.1
CVSS3 Base Metrics CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector Network
Attack Complexity High
Privileges Required None
User Interaction None
Scope Unchanged
Confidentiality High
Integrity Impact High
Availability Impact High

Affected Packages State

Platform Package State
Red Hat Virtualization 4 postgresql-jdbc Will not fix
Red Hat Mobile Application Platform On-Premise 4 millicore Not affected
Red Hat Enterprise Linux 7 postgresql-jdbc Affected
Red Hat Enterprise Linux 6 postgresql-jdbc Will not fix
Red Hat Ansible Tower 3 for RHEL 7 postgresql96 Not affected


Red Hat would like to thank the PostgreSQL project for reporting this issue.


Applications using postgresql-jdbc should have their SSL configuration reviewed to ensure that host name verification is not disabled and only trusted CAs are accepted.

This vulnerability only impacts usage of postgresql-jdbc with a non-default SSL Factory, provided by the `sslfactory` parameter. If this parameter is not given, the default LibPQFactory is used, which is not vulnerable.

External References

Last Modified