pgsql: Reject certificates with embedded NULLs in the commonName field. - Mailing list pgsql-committers

Log Message:
-----------
Reject certificates with embedded NULLs in the commonName field. This stops
attacks where an attacker would put <attack>\0<propername> in the field and
trick the validation code that the certificate was for <attack>.

This is a very low risk attack since it reuqires the attacker to trick the
CA into issuing a certificate with an incorrect field, and the common
PostgreSQL deployments are with private CAs, and not external ones. Also,
default mode in 8.4 does not do any name validation, and is thus also not
vulnerable - but the higher security modes are.

Backpatch all the way. Even though versions 8.3.x and before didn't have
certificate name validation support, they still exposed this field for
the user to perform the validation in the application code, and there
is no way to detect this problem through that API.

Security: CVE-2009-4034

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
    pgsql/src/backend/libpq:
        be-secure.c (r1.74.2.3 -> r1.74.2.4)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/be-secure.c?r1=1.74.2.3&r2=1.74.2.4)
    pgsql/src/interfaces/libpq:
        fe-secure.c (r1.89.2.1 -> r1.89.2.2)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-secure.c?r1=1.89.2.1&r2=1.89.2.2)