From nobody Wed Nov 30 00:46:58 2022 X-Original-To: freebsd-security-notifications@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NMLBV4ZlVz4j2gt for ; Wed, 30 Nov 2022 00:46:58 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NMLBV3M1bz4Dbk; Wed, 30 Nov 2022 00:46:58 +0000 (UTC) (envelope-from security-advisories@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1669769218; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc; bh=PE8+p24Wl+W9Dx5WmU6DGNoC2h5QED7uRNVEV01acIE=; b=B3emhveBCo3wDaB1GZmBWM8IS1K27KdBIxGM91gtNC0A2Y+EoolsV3sSHz+1YXJJGE4V8p 6LT7M2PaZVMqnico/mZiiGgEZ0Uy8+h30YSNVtFdoTmT6F2RDp+zQ5N82Y8FoQH7D+AlHw gFmQlg0ouuRTXsYb8DK5FYJEZRannM0km//n9EHNvt3qqo/nojR31ngFYH2abIU5Wb6itH /gcK7GqADevOgJp/WZ+4JUXr2J9mess4q8HXWj5yjTaxRKyJyhTQ4Sh1NrUD+hn7mj3YXp dYbrAphnAh4BEk4d6HOzbhPMT52cAu6mldygyddde5OpxvCtpItF+irNMukVXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1669769218; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc; bh=PE8+p24Wl+W9Dx5WmU6DGNoC2h5QED7uRNVEV01acIE=; b=k+y1J0D/eOZPw+H2nxi/ZK3oJeqWQTbxjaPKBVleZwWJBX3tFDB6qpeMWXDDTsWqzJxNA4 jE4bQPvvwQ4k8r3DYAprYEIAKoz8ieEQKXUc4lJ46bNr4xYTKWnT4ccg+9/9WZEFQb5BtJ WpBJInunaICMpBGTS99ztglG3hogBqNkFKooO1xgnreZ2ONZvDgLZQzFDXkHilvtzIXNOU LxrchpVbBc/CGnNqhT1zpG/Faz8xI0WhZzcAOigHx9PKl8NYTZzhTKQI8lxB9+EiR618DS Q+keYPIg8lmeLu1dwaZPJqYTBCW4Yz2NNh9vyXHoVThAlPWjqg1+seFquMMDXQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1669769218; a=rsa-sha256; cv=none; b=W/OZ5ezFoCr0eVaKICoOgjUwJzdqcOmAfBK6mu18Ucnx0a2viFOIIVG5XbJ+SDTkWz3fSc fE6tPy9RqWY0ayn3MMcYtAELlbgSM7iIlUEMNSulGDTVQmaZ8j6FrnliX37QSwcG0k38Kt oLUyc3GSkEult6Ol8pCvojtA9Zg9j2eHJdC8kdKq+sEIxHDKgk8pqJmhwPK/veCpSQ+LtF FAGSNJZFzuX/1uXYuWAV6AEKgmDHBO1GbGcc0SMIKUNWIDuBK+mT3Vg+w5QEe/aGHC16yo 7jcdxSBCSw8a/26sIspwBrUzNvWQFGlaS+pthgtvZc4mbR6H8MVHGrL1CT0xgA== Received: by freefall.freebsd.org (Postfix, from userid 945) id 4C2721C376; Wed, 30 Nov 2022 00:46:58 +0000 (UTC) From: FreeBSD Security Advisories To: FreeBSD Security Advisories Subject: FreeBSD Security Advisory FreeBSD-SA-22:14.heimdal [REVISED] Reply-To: freebsd-security@freebsd.org Precedence: bulk Message-Id: <20221130004658.4C2721C376@freefall.freebsd.org> Date: Wed, 30 Nov 2022 00:46:58 +0000 (UTC) X-ThisMailContainsUnwantedMimeParts: N List-Id: Moderated Security Notifications [moderated, low volume] List-Archive: https://lists.freebsd.org/archives/freebsd-security-notifications List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-security-notifications@freebsd.org X-BeenThere: freebsd-security-notifications@freebsd.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-22:14.heimdal Security Advisory The FreeBSD Project Topic: Multiple vulnerabilities in Heimdal [REVISED] Category: contrib Module: heimdal Announced: 2022-11-15 Revised: 2022-11-29 Affects: All supported versions of FreeBSD. Corrected: 2022-11-15 21:15:35 UTC (stable/13, 13.1-STABLE) 2022-11-16 01:50:27 UTC (releng/13.1, 13.1-RELEASE-p4) 2022-11-15 21:16:56 UTC (stable/12, 12.4-STABLE) 2022-11-16 01:47:57 UTC (releng/12.4, 12.4-RC2-p1) 2022-11-16 01:40:21 UTC (releng/12.3, 12.3-RELEASE-p9) CVE Name: CVE-2019-14870, CVE-2022-3437, CVE-2022-42898, CVE-2022-44640, CVE-2021-44758 0. Revision history v1.0 2022-11-15 Initial release. v1.1 2022-11-29 Updated with reference to FreeBSD-EN-22:28.heimdal. For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background Heimdal implements the Kerberos 5 network authentication protocols. A Key Distribution Center (KDC) is trusted by all principals registered in that administrative "realm" to store a secret key in confidence, of which, the proof of knowledge is used to verify the authenticity of a principal. II. Problem Description Multiple security vulnerabilities have been discovered in the Heimdal implementation of the Kerberos 5 network authentication protocols and KDC. - - CVE-2022-42898 PAC parse integer overflows - - CVE-2022-3437 Overflows and non-constant time leaks in DES{,3} and arcfour - - CVE-2021-44758 NULL dereference DoS in SPNEGO acceptors - - CVE-2022-44640 Heimdal KDC: invalid free in ASN.1 codec - - CVE-2019-14870 Validate client attributes in protocol-transition - - CVE-2019-14870 Apply forwardable policy in protocol-transition - - CVE-2019-14870 Always lookup impersonate client in DB III. Impact A malicious actor with control of the network between a client and a service using Kerberos for authentication can impersonate either the client or the service, enabling a man-in-the-middle (MITM) attack circumventing mutual authentication. Note that, while CVE-2022-44640 is a severe vulnerability, possibly enabling remote code execution on other platforms, the version of Heimdal included with the FreeBSD base system cannot be exploited in this way on FreeBSD. IV. Workaround No workaround is available, but only systems using Kerberos are affected. V. Solution Upgrade your vulnerable system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date. A reboot is recommended. Perform one of the following: 1) To update your vulnerable system via a binary patch: Systems running a RELEASE version of FreeBSD on the amd64, i386, or (on FreeBSD 13 and later) arm64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install A reboot is recommended. 2) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. # fetch https://security.FreeBSD.org/patches/SA-22:14/heimdal.patch # fetch https://security.FreeBSD.org/patches/SA-22:14/heimdal.patch.asc # gpg --verify heimdal.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch < /path/to/patch c) The original revision of this advisory included a patch which renders the KDC inoperative. This was corrected in FreeBSD-EN-22:28.heimdal. Systems using the KDC must download and verify an additional patch: # fetch https://security.FreeBSD.org/patches/EN-22:28/heimdal.patch # fetch https://security.FreeBSD.org/patches/EN-22:28/heimdal.patch.asc # gpg --verify heimdal.patch.asc d) Apply the additional patch. Execute the following commands as root: # cd /usr/src # patch < /path/to/patch e) Recompile the operating system using buildworld and installworld as described in . Restart all daemons that use the Kerberos, or reboot the system. VI. Correction details This issue is corrected by the corresponding Git commit hash or Subversion revision number in the following stable and release branches: Branch/path Hash Revision - ------------------------------------------------------------------------- stable/13/ d0b6550173d2 stable/13-n253097 releng/13.1/ a1e014e89282 releng/13.1-n250170 stable/12/ r372752 releng/12.4/ r372755 releng/12.3/ r372753 - ------------------------------------------------------------------------- For FreeBSD 13 and later: Run the following command to see which files were modified by a particular commit: # git show --stat Or visit the following URL, replacing NNNNNN with the hash: To determine the commit count in a working tree (for comparison against nNNNNNN in the table above), run: # git rev-list --count --first-parent HEAD For FreeBSD 12 and earlier: Run the following command to see which files were modified by a particular revision, replacing NNNNNN with the revision number: # svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base Or visit the following URL, replacing NNNNNN with the revision number: VII. References The latest revision of this advisory is available at -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAmOGlpAACgkQ05eS9J6n 5cJFGQ//TbsJox2faNwQaBoQy/gFSP6TgauZTZJR5A5Y6bRMcvkNJyl3KIM2XlWD W+lJlxL7kERjv9zD6iI8rns4+FOO2p9f4ICZsWy88ABQrmpuz2N22MSd8NyXeRv0 30HyftaUMZdAPHVk5Piu7l3U6S4tPiO1BZEoMucG8cby1eWlPMtuH3K/0/CLZmPc F8U+oRDwB5KnZgP39JmvejvGoXik1lhCrvaLZ5fG1QEmyb1xtjHfT+QSkh9FWLxz jrHfwgpZFERprpMzqZAicbinV/LjZMfEbckJygzGNzSTTPD+uqT/jDmY+iHnkdF1 Lw9R8pJoJIpvckRrPLQIOZZuz/Xd4FRB7Gc/q4/x4HTP/8y/x1uKZmcbrh86W9xu 9jCLMgpqETEjHhqADX7Z4+7oxhCPmgSJP8dX5o0HvORs4bqqxbkLqkCsp8QXdcES vftJGgpt1IPO8MBcr4pG6+cEcZQuk7qX0/D3PArxLkwU2coimP2MmjxyeWBX5GrI zgdF2HiUYvuZXyt1FMgve+8JkS1RYEE+yPWeOJ5RnIuHnIaNTD81o1gIYuFL3ECb UAREi6FYskzeJQ/W2ZRMwQPGMPDQI901+msfStjxgx92rKhxLW+rDsg0EUsApoOv DzIaeCtOGCZMG/mLvVhOLYbqmFrHDbWy8cMoSti/lnx7OdLpnn4= =L299 -----END PGP SIGNATURE----- From nobody Wed Feb 8 19:08:33 2023 X-Original-To: freebsd-security-notifications@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PBqKF2Q7kz3np2p for ; Wed, 8 Feb 2023 19:08:33 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PBqKF1vhvz467S; Wed, 8 Feb 2023 19:08:33 +0000 (UTC) (envelope-from security-advisories@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675883313; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc; bh=Ab5uT2bsGKVQJaKagd651jR+NqTWu3spOOSpNdo3EEA=; b=tmsC7scLvxhezmYi618xvupNJstc3IAPgiK+aUr4PT3V/NGZRcHYQO5eXwA5tumPqFEFrw /SpxmtNIZBkhXPNVpHXyLPJTJKjDYuxtPAJ7VKNUJA0aNJ7j0DQR9msl70zJ7iJb0AJJAG tKv1XWSCS9vQhedNmUi5Yf5JrdmOVazygJP2KRojCplQQ+w9QeNXzbbkcuH/oz6zagWLHX CLVEdQWPqevsrnJp/m4NOUieXrQE9u5RzoIm4dF8C93Uak/iui3vDs5HWmuX+jkAk6mA3Q tP4nMMKRVtpz/5BSvto1iy9lI/Nl/8Ct18kfOknIQL6OrvmPodn6T5sBTbHMVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675883313; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc; bh=Ab5uT2bsGKVQJaKagd651jR+NqTWu3spOOSpNdo3EEA=; b=vA0xcLT4VqY+OYMy3IvbImo5P9iaR+eoHF6DeQEr4pHPjPmuVaIIzcGk5fQu2Fx5d7WAk/ vK7JlLHKqVklPPE+uRV4XOUMv7YNQrnovfXWKBHux4xO/RUntDDhrt9sTnlDZzoWEsnxPX GEn+1/RZ6tKtlabBUjm17Hch0rNV8OG5nqSMpnIzUst2H9S3hn/LA1+0rR2B/65RPpmFVl SIInfLIJoWLi5NoEZx/mKwUzKpyS9z+9jCZSDJFgoqDsBBpGnxTUK70q+68oWiD7N/NXCI yeuoWy0xw9MuFD4rvpwzd1DYQPiKkhEtbwak1hEXTElwFexLaUbgG/xR9tHeSA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1675883313; a=rsa-sha256; cv=none; b=PcjNTJiQfyBGI476F2xBE1BWkj3bRVJS3xqTnSZ/5z7tB0rFS34MHnZECsGYLwX8KT5re6 KcUIdwzjeZMSKhfjp6sh5ke4eDRvYBACaJZ8M+lnZ+MUU2Ey1qlWh/AV8E9tl1W6ioMg1R +O2+TmlJpAS1oTxQYhH/AY/JtDe5HEtVnC3Q6CqyYeukFWfaZ2GISHkNnYNyZDWUe+mKeV t/B5KQdeUCOaHx0CcMxO7WRa5PCbCPBtxzTs0mQ3megtMqpti2fZp2tIgGU1mnfgpC6pyN SCvLat6FIutfIaO5YrDw9yH8007qv4zFtRIC/7gvupjhEwWH8bEWV8ZxO6Ja2Q== Received: by freefall.freebsd.org (Postfix, from userid 945) id 283D087C3; Wed, 8 Feb 2023 19:08:33 +0000 (UTC) From: FreeBSD Security Advisories To: FreeBSD Security Advisories Subject: FreeBSD Security Advisory FreeBSD-SA-23:01.geli Reply-To: freebsd-security@freebsd.org Precedence: bulk Message-Id: <20230208190833.283D087C3@freefall.freebsd.org> Date: Wed, 8 Feb 2023 19:08:33 +0000 (UTC) X-ThisMailContainsUnwantedMimeParts: N List-Id: Moderated Security Notifications [moderated, low volume] List-Archive: https://lists.freebsd.org/archives/freebsd-security-notifications List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-security-notifications@freebsd.org X-BeenThere: freebsd-security-notifications@freebsd.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-23:01.geli Security Advisory The FreeBSD Project Topic: GELI silently omits the keyfile if read from stdin Category: core Module: geli Announced: 2023-02-08 Credits: Nathan Dorfman Affects: All supported versions of FreeBSD. Corrected: 2023-02-08 18:03:19 UTC (stable/13, 13.1-STABLE) 2023-02-08 18:06:31 UTC (releng/13.1, 13.1-RELEASE-p6) 2023-02-08 18:05:45 UTC (stable/12, 12.4-STABLE) 2023-02-08 18:30:27 UTC (releng/12.4, 12.4-RELEASE-p1) 2023-02-08 18:28:31 UTC (releng/12.3, 12.3-RELEASE-p11) CVE Name: CVE-2023-0751 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background GELI is a block device-layer disk encryption utility. It uses a random master key to perform symmetric cryptography on sectors. The master key is encrypted using a user key, which might consist of up to two components: a user passphrase and a key file. The key file might be read from a file or a standard input. GELI also allows to initialization of multiple devices with a single command. II. Problem Description When GELI reads a key file from a standard input, it doesn't store it anywhere. If the user tries to initialize multiple providers at once, for the second and subsequent devices the standard input stream will be already empty. In this case, GELI silently uses a NULL key as the user key file. If the user used only a key file without a user passphrase, the master key was encrypted with an empty key file. This might not be noticed if the devices were also decrypted in a batch operation. III. Impact Some GELI providers might be silently encrypted with a NULL key file. IV. Workaround On affected systems, instead of initializing GELI devices in a batch operation, the recommended way is to do this operation on a single provider. V. Solution If the system already has the device initialized with a null key, the master key has to be encrypted: echo -n | geli setkey -k- -p -K /path/to/keyfile -P /dev/provider Upgrade your vulnerable system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date, and reboot. Perform one of the following: 1) To update your vulnerable system via a binary patch: Systems running a RELEASE version of FreeBSD on the amd64, i386, or (on FreeBSD 13 and later) arm64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # shutdown -r +10min "Rebooting for a security update" 2) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. # fetch https://security.FreeBSD.org/patches/SA-23:01/geli.patch # fetch https://security.FreeBSD.org/patches/SA-23:01/geli.patch.asc # gpg --verify geli.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch < /path/to/patch c) Recompile your kernel as described in and reboot the system. VI. Correction details This issue is corrected by the corresponding Git commit hash or Subversion revision number in the following stable and release branches: Branch/path Hash Revision - ------------------------------------------------------------------------- stable/13/ 88bb08452ee3 stable/13-n254412 releng/13.1/ 98933c7013a5 releng/13.1-n250179 stable/12/ r372910 releng/12.4/ r372917 releng/12.3/ r372913 - ------------------------------------------------------------------------- For FreeBSD 13 and later: Run the following command to see which files were modified by a particular commit: # git show --stat Or visit the following URL, replacing NNNNNN with the hash: To determine the commit count in a working tree (for comparison against nNNNNNN in the table above), run: # git rev-list --count --first-parent HEAD For FreeBSD 12 and earlier: Run the following command to see which files were modified by a particular revision, replacing NNNNNN with the revision number: # svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base Or visit the following URL, replacing NNNNNN with the revision number: VII. References The latest revision of this advisory is available at -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEthUnfoEIffdcgYM7bljekB8AGu8FAmPj8B8ACgkQbljekB8A Gu8Q2g//WfBcATFcQsXQC/fO8oGa90pZl3+mBIBabMO7bMsZ3jzmsZM0DjEuztDM sOY6g9ExN5Fmh4O6Mvg12FjtsbJwp/4KxsrfjG3F8aTKjTKTdbBqhDodwQwCL9ZF u+qkNMrtdqFvigGqmCpKq6vC7kYx12NVFvr4X81kgBmwCOPUKlD351lnkQKv0C5B G3HeLdQb7stMRcnHWcqOw7m98aRSU0gE2/9BAMqfvtVWboa6LrdF6PQVav8Lq417 qh8Md71IAAWyFm8jcOtsX949KdtI1kcwDbVyuO5mT6TNFTuEu/lIx78/YpvGVZUt 1a7FAkiekr6c19xC01o6muc6E1XiwxO/vQMMwEsW9lv+N2fm4d7EGUP3nvFZTzgt OOKVORcqEsdZj92/UDdUXsIFV7fja0t7rGUXhI/YTAtnOvESTvDkUzfNQ3fxIMcG COFQdxJ0+P2oItMSeY2dlN8A/z41N6BqAilmg/LxuzZkCblC8q0JxLoAsAEydT4j RHA7dTwFNeM+6kVluERX302l6JGogg6mB+o/O+vqKWfDrvEzv7CLHEGnBT6lcAkX x1RQwXFd84fHwWXAffsUNKxrQe0QI+dbPcGH0YtHZntno1Azds3oVBAFa5nUcYVD 3A8ShP18hwkVLRyG9680fSD5cQwYKZpLuasujikLqnme/PkYDy4= =6d7v -----END PGP SIGNATURE-----