CVE Vulnerabilities

CVE-2014-3522

Improper Validation of Certificate with Host Mismatch

Published: Aug 19, 2014 | Modified: Oct 30, 2018
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
4 MEDIUM
AV:N/AC:H/Au:N/C:P/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu

The Serf RA layer in Apache Subversion 1.4.0 through 1.7.x before 1.7.18 and 1.8.x before 1.8.10 does not properly handle wildcards in the Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof servers via a crafted certificate.

Weakness

The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.

Affected Software

Name Vendor Start Version End Version
Subversion Apache 1.6.10 1.6.10
Subversion Apache 1.6.19 1.6.19
Subversion Apache 1.8.2 1.8.2
Subversion Apache 1.4.5 1.4.5
Subversion Apache 1.7.3 1.7.3
Subversion Apache 1.6.20 1.6.20
Subversion Apache 1.7.17 1.7.17
Subversion Apache 1.8.0 1.8.0
Subversion Apache 1.4.2 1.4.2
Subversion Apache 1.6.2 1.6.2
Subversion Apache 1.7.1 1.7.1
Subversion Apache 1.7.11 1.7.11
Subversion Apache 1.7.16 1.7.16
Subversion Apache 1.6.18 1.6.18
Subversion Apache 1.6.16 1.6.16
Subversion Apache 1.5.5 1.5.5
Subversion Apache 1.7.4 1.7.4
Subversion Apache 1.6.21 1.6.21
Subversion Apache 1.6.5 1.6.5
Subversion Apache 1.7.6 1.7.6
Subversion Apache 1.5.3 1.5.3
Subversion Apache 1.4.0 1.4.0
Subversion Apache 1.8.1 1.8.1
Subversion Apache 1.4.4 1.4.4
Subversion Apache 1.5.7 1.5.7
Subversion Apache 1.4.6 1.4.6
Subversion Apache 1.8.9 1.8.9
Subversion Apache 1.7.9 1.7.9
Subversion Apache 1.7.12 1.7.12
Subversion Apache 1.6.3 1.6.3
Subversion Apache 1.6.8 1.6.8
Subversion Apache 1.7.10 1.7.10
Subversion Apache 1.8.5 1.8.5
Subversion Apache 1.6.13 1.6.13
Subversion Apache 1.7.7 1.7.7
Subversion Apache 1.6.0 1.6.0
Subversion Apache 1.5.8 1.5.8
Subversion Apache 1.5.2 1.5.2
Subversion Apache 1.6.7 1.6.7
Subversion Apache 1.6.12 1.6.12
Subversion Apache 1.8.6 1.8.6
Subversion Apache 1.7.2 1.7.2
Subversion Apache 1.6.1 1.6.1
Subversion Apache 1.6.4 1.6.4
Subversion Apache 1.7.13 1.7.13
Subversion Apache 1.8.4 1.8.4
Subversion Apache 1.6.23 1.6.23
Subversion Apache 1.8.3 1.8.3
Subversion Apache 1.7.8 1.7.8
Subversion Apache 1.4.3 1.4.3
Subversion Apache 1.8.7 1.8.7
Subversion Apache 1.6.15 1.6.15
Subversion Apache 1.5.4 1.5.4
Subversion Apache 1.7.14 1.7.14
Subversion Apache 1.6.11 1.6.11
Subversion Apache 1.7.5 1.7.5
Subversion Apache 1.6.14 1.6.14
Subversion Apache 1.5.1 1.5.1
Subversion Apache 1.7.15 1.7.15
Subversion Apache 1.6.17 1.6.17
Subversion Apache 1.5.6 1.5.6
Subversion Apache 1.5.0 1.5.0
Subversion Apache 1.6.6 1.6.6
Subversion Apache 1.6.9 1.6.9
Subversion Apache 1.4.1 1.4.1
Subversion Apache 1.8.8 1.8.8
Subversion Apache 1.7.0 1.7.0

Extended Description

Even if a certificate is well-formed, signed, and follows the chain of trust, it may simply be a valid certificate for a different site than the site that the product is interacting with. If the certificate’s host-specific data is not properly checked - such as the Common Name (CN) in the Subject or the Subject Alternative Name (SAN) extension of an X.509 certificate - it may be possible for a redirection or spoofing attack to allow a malicious host with a valid certificate to provide data, impersonating a trusted host. In order to ensure data integrity, the certificate must be valid and it must pertain to the site that is being accessed. Even if the product attempts to check the hostname, it is still possible to incorrectly check the hostname. For example, attackers could create a certificate with a name that begins with a trusted name followed by a NUL byte, which could cause some string-based comparisons to only examine the portion that contains the trusted name. This weakness can occur even when the product uses Certificate Pinning, if the product does not verify the hostname at the time a certificate is pinned.

Potential Mitigations

References