From owner-svn-ports-head@FreeBSD.ORG Fri Aug 16 05:35:01 2013 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DF3DC208; Fri, 16 Aug 2013 05:35:00 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CD0FF2FFC; Fri, 16 Aug 2013 05:35:00 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r7G5Z09S007105; Fri, 16 Aug 2013 05:35:00 GMT (envelope-from remko@svn.freebsd.org) Received: (from remko@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r7G5Z0Sn007103; Fri, 16 Aug 2013 05:35:00 GMT (envelope-from remko@svn.freebsd.org) Message-Id: <201308160535.r7G5Z0Sn007103@svn.freebsd.org> From: Remko Lodder Date: Fri, 16 Aug 2013 05:35:00 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r324791 - head/security/vuxml X-SVN-Group: ports-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Aug 2013 05:35:01 -0000 Author: remko (src,doc committer) Date: Fri Aug 16 05:35:00 2013 New Revision: 324791 URL: http://svnweb.freebsd.org/changeset/ports/324791 Log: Correct polarssl entry, the lines were way to long, indentation was incorrect, and the topic description does not need too many details since that is explained in the description itself. Also correct the url's since c comes before u ;-) Prodded by: stas Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Fri Aug 16 02:28:50 2013 (r324790) +++ head/security/vuxml/vuln.xml Fri Aug 16 05:35:00 2013 (r324791) @@ -83,7 +83,7 @@ Note: Please add new entries to the beg - polarssl -- denial of service through unterminated loop in certificate parser + polarssl -- denial of service vulnerability polarssl @@ -94,21 +94,33 @@ Note: Please add new entries to the beg

Paul Bakker reports:

-
A bug in the logic of the parsing of PEM encoded certificates in x509parse_crt() can result in an infinite loop, thus hogging processing power. -
- While parsing a Certificate message during the SSL/TLS handshake, PolarSSL extracts the presented certificates and sends them on to be parsed. As the RFC specifies that the certificates in the Certificate message are always X.509 certificates in DER format, bugs in the decoding of PEM certificates should normally not be triggerable via the SSL/TLS handshake. -
- Versions of PolarSSL prior to 1.1.7 in the 1.1 branch and prior to 1.2.8 in the 1.2 branch call the generic x509parse_crt() function for parsing during the handshake. x509parse_crt() is a generic functions that wraps parsing of both PEM-encoded and DER-formatted certificates. As a result it is possible to craft a Certificate message that includes a PEM encoded certificate in the Certificate message that triggers the infinite loop.
+
A bug in the logic of the parsing of PEM encoded certificates in + x509parse_crt() can result in an infinite loop, thus hogging processing + power.
+
While parsing a Certificate message during the SSL/TLS handshake, + PolarSSL extracts the presented certificates and sends them on to + be parsed. As the RFC specifies that the certificates in the + Certificate message are always X.509 certificates in DER format, + bugs in the decoding of PEM certificates should normally not be + triggerable via the SSL/TLS handshake.
+
Versions of PolarSSL prior to 1.1.7 in the 1.1 branch and prior + to 1.2.8 in the 1.2 branch call the generic x509parse_crt() + function for parsing during the handshake. x509parse_crt() is a + generic functions that wraps parsing of both PEM-encoded and + DER-formatted certificates. As a result it is possible to craft + a Certificate message that includes a PEM encoded certificate in + the Certificate message that triggers the infinite loop.

- https://polarssl.org/tech-updates/security-advisories/polarssl-security-advisory-2013-03 CVE-2013-4623 + https://polarssl.org/tech-updates/security-advisories/polarssl-security-advisory-2013-03 2013-06-21 2013-08-13 + 2013-08-15