From owner-svn-ports-head@freebsd.org  Tue Feb  5 14:39:14 2019
Return-Path: <owner-svn-ports-head@freebsd.org>
Delivered-To: svn-ports-head@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B9FC14BB406;
 Tue,  5 Feb 2019 14:39:14 +0000 (UTC) (envelope-from ler@FreeBSD.org)
Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org
 [IPv6:2610:1c1:1:606c::19:3])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits)
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "mxrelay.nyi.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 1CD7975A3F;
 Tue,  5 Feb 2019 14:39:14 +0000 (UTC) (envelope-from ler@FreeBSD.org)
Received: from repo.freebsd.org (repo.freebsd.org
 [IPv6:2610:1c1:1:6068::e6a:0])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 0C4001F3E5;
 Tue,  5 Feb 2019 14:39:14 +0000 (UTC) (envelope-from ler@FreeBSD.org)
Received: from repo.freebsd.org ([127.0.1.37])
 by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x15EdDsR034669;
 Tue, 5 Feb 2019 14:39:13 GMT (envelope-from ler@FreeBSD.org)
Received: (from ler@localhost)
 by repo.freebsd.org (8.15.2/8.15.2/Submit) id x15EdDCN034668;
 Tue, 5 Feb 2019 14:39:13 GMT (envelope-from ler@FreeBSD.org)
Message-Id: <201902051439.x15EdDCN034668@repo.freebsd.org>
X-Authentication-Warning: repo.freebsd.org: ler set sender to ler@FreeBSD.org
 using -f
From: Larry Rosenman <ler@FreeBSD.org>
Date: Tue, 5 Feb 2019 14:39:13 +0000 (UTC)
To: ports-committers@freebsd.org, svn-ports-all@freebsd.org,
 svn-ports-head@freebsd.org
Subject: svn commit: r492242 - head/security/vuxml
X-SVN-Group: ports-head
X-SVN-Commit-Author: ler
X-SVN-Commit-Paths: head/security/vuxml
X-SVN-Commit-Revision: 492242
X-SVN-Commit-Repository: ports
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Rspamd-Queue-Id: 1CD7975A3F
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-2.96 / 15.00];
 local_wl_from(0.00)[FreeBSD.org];
 NEURAL_HAM_MEDIUM(-1.00)[-0.999,0];
 NEURAL_HAM_SHORT(-0.96)[-0.958,0];
 ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US];
 NEURAL_HAM_LONG(-1.00)[-0.999,0]
X-BeenThere: svn-ports-head@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SVN commit messages for the ports tree for head
 <svn-ports-head.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/svn-ports-head>, 
 <mailto:svn-ports-head-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-ports-head/>
List-Post: <mailto:svn-ports-head@freebsd.org>
List-Help: <mailto:svn-ports-head-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/svn-ports-head>,
 <mailto:svn-ports-head-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2019 14:39:14 -0000

Author: ler
Date: Tue Feb  5 14:39:13 2019
New Revision: 492242
URL: https://svnweb.freebsd.org/changeset/ports/492242

Log:
  mail/dovecot: Suitable client certificate can be used to login as other user
  
  update vuxml

Modified:
  head/security/vuxml/vuln.xml

Modified: head/security/vuxml/vuln.xml
==============================================================================
--- head/security/vuxml/vuln.xml	Tue Feb  5 14:34:26 2019	(r492241)
+++ head/security/vuxml/vuln.xml	Tue Feb  5 14:39:13 2019	(r492242)
@@ -58,6 +58,66 @@ Notes:
   * Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
 -->
 <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+  <vuln vid="1340fcc1-2953-11e9-bc44-a4badb296695">
+    <topic>mail/dovecot -- Suitable client certificate can be used to login as other user</topic>
+    <affects>
+      <package>
+	<name>dovecot</name>
+	<range><lt>2.3.4.1</lt></range>
+      </package>
+    </affects>
+    <description>
+      <body xmlns="http://www.w3.org/1999/xhtml">
+	<p>SO-AND-SO reports:</p>
+	<blockquote cite="https://www.mail-archive.com/dovecot@dovecot.org/msg76117.html">
+	  <p>Normally Dovecot is configured to authenticate
+imap/pop3/managesieve/submission clients using regular username/password
+combination. Some installations have also required clients to present a
+trusted SSL certificate on top of that. It's also possible to configure
+Dovecot to take the username from the certificate instead of from the
+user provided authentication. It's also possible to avoid having a
+password at all, only trusting the SSL certificate.
+
+If the provided trusted SSL certificate is missing the username field,
+Dovecot should be failing the authentication. However, the earlier
+versions will take the username from the user provided authentication
+fields (e.g. LOGIN command). If there is no additional password
+verification, this allows the attacker to login as anyone else in the
+system.
+
+This affects only installations using:
+
+auth_ssl_require_client_cert = yes
+auth_ssl_username_from_cert = yes
+
+Attacker must also have access to a valid trusted certificate without
+the ssl_cert_username_field in it. The default is commonName, which
+almost certainly exists in all certificates. This could happen for
+example if ssl_cert_username_field is a field that normally doesn't
+exist, and attacker has access to a web server's certificate (and key),
+which is signed with the same CA.
+
+Attack can be migitated by having the certificates with proper Extended
+Key Usage, such as 'TLS Web Server' and 'TLS Web Server Client'.
+
+Also, ssl_cert_username_field setting was ignored with external SMTP
+AUTH, because none of the MTAs (Postfix, Exim) currently send the
+cert_username field. This may have allowed users with trusted
+certificate to specify any username in the authentication. This does not
+apply to Dovecot Submission service.</p>
+	</blockquote>
+      </body>
+    </description>
+    <references>
+      <url>https://www.mail-archive.com/dovecot@dovecot.org/msg76117.html</url>
+      <cvename>CVE-2019-3814</cvename>
+    </references>
+    <dates>
+      <discovery>2019-01-16</discovery>
+      <entry>2019-02-05</entry>
+    </dates>
+  </vuln>
+
   <vuln vid="5d8c0876-2716-11e9-9446-b7f8544ce15c">
     <topic>typo3 -- multiple vulnerabilities</topic>
     <affects>