CVE-2014-1492: Input Validation
In a wildcard certificate, the wildcard character should not be embedded within the U-label of an internationalized domain name. This was not properly implemented in NSS, as a result it did not handle IDNA domain prefixes according to RFC 6125, section 6.4.3 "Checking of Wildcard Certificates". http://tools.ietf.org/html/rfc6125#section-6.4.3
Upstream patch: https://hg.mozilla.org/projects/nss/rev/15ea62260c21 https://hg.mozilla.org/projects/nss/rev/2ffa40a3ff55 https://hg.mozilla.org/projects/nss/rev/709d4e597979
Upstream bug (not public): https://bugzilla.mozilla.org/showbug.cgi?id=903885
This issue was fixed upstream in NSS 3.16: https://developer.mozilla.org/en-US/docs/NSS/NSS3.16releasenotes
Other sources
The certTestHostName function in lib/certdb/certdb.c in the certificate-checking implementation in Mozilla Network Security Services (NSS) before 3.16 accepts a wildcard character that is embedded in an internationalized domain name's U-label, which might allow man-in-the-middle attackers to spoof SSL servers via a crafted certificate.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/nssto a version that resolves this vulnerability.Fixed in 3.16 - Upgrade
Upgrade
Mozilla Network Security Services (NSS)to a version that resolves this vulnerability.Fixed in 3.16
Event History
Frequently Asked Questions
What is the severity of CVE-2014-1492?
CVE-2014-1492 has been rated as a moderate severity vulnerability due to improper validation of wildcard certificates.
How do I fix CVE-2014-1492?
To fix CVE-2014-1492, update the affected NSS package to version 3.16 or later.
Which software versions are vulnerable to CVE-2014-1492?
Vulnerable software versions include NSS versions up to 3.15.5 and specific ranges of 3.2 to 3.9.
What impact does CVE-2014-1492 have on secure communications?
CVE-2014-1492 could allow attackers to exploit wildcard certificates inadequately validated, potentially compromising secure communications.
Is there a workaround for CVE-2014-1492 while I update?
A temporary workaround is to avoid the use of wildcard certificates in internationalized domain names until the update is applied.