From nobody Tue Jan 16 17:10:40 2024 X-Original-To: dev-commits-ports-all@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 4TDwWN53w2z57dLn; Tue, 16 Jan 2024 17:10:40 +0000 (UTC) (envelope-from git@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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TDwWN4dRZz4hp7; Tue, 16 Jan 2024 17:10:40 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705425040; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=yx5sPu//dfJUT48RJ8H2EVPMyMCt+fTfGOP05ACPdqE=; b=XgsltVX+bHXxl+IJHxhA5Tf0MrVlhP/n+5w+OXBC7kihomQLZvOGU1n/AAqYWdnK3fQYBN sw4vjhJKbsdqA8dTsC8Be1zNdWzxTSPjokzgbCEjnGGQ2sYmTKMa8vZrYOcbVWLsGibjyV trLNv/h4gzHpcyesjpalACSwNnB39tZQyGGwxtZT6HN0VmRgMAKE59KKUpjUC+AZ9O26lv 2K4+t18D+RLpzyo2WAxrnKQ0XG563zKVCOnvSoYs3JGImEnw/4+jLXM8WHV5dRrv8x/oy4 5YFBrNIh5BEB1OdrJ4E3aiDzVBj8BZwGEA7tY+z3QeP4pey4mV6je3Su8qx36w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705425040; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=yx5sPu//dfJUT48RJ8H2EVPMyMCt+fTfGOP05ACPdqE=; b=ZkXKl0Lyd6j3kEghYykvXLKfZh2csT3pHN9YKqNam2fWwNCiIq/Du9gYh9ftlrzIG1DLEG w2g3LJk6niLJWnQ8sJTpR2W+3fLcLF9rWVn7ioELTrjmcZGWJ67AP/Uy/IwC6JmUsD/0v4 P2umh2V4ja2Zl+1L/NdBTrejNSLoiKHkS/yBZLd1tS4OCRjCetar/+tXG3JKz3nTgihmIO 8LLVh+24EUs4orwjvmjC+wUv6pXdb4FqWZVEuL1W7dOhpkYPSN2f9W8oi3U1T0mQ4pf7y/ Lx1OKd/eU06fUo3+5xrXC3xBfH0kBZaNjys/sFq7jfxuP5rQBPO74dgzRZXwrQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1705425040; a=rsa-sha256; cv=none; b=GUXxYm1OgzJ+feiHYgNjuRWizWvqEGZoFA4WjdOwYDCxUiXaaTl70td4F8cbgM/sMkVFpq mofh/D37DkCueBorTs5G25/rMIVF4ZR0KLZbHsqn3xd2JIUZKbKbXXyrmZanpz2hpRFwCx htxxKAkao8GYOYHczpXDou3CVzTAK5Fd0fqCtkaJmKndxyEzdyVepbe5/r587LQJjCl63I 1/SXytFYYp8m3If7BKL9SPDC/0KPB9FKRytpg/W6oze2qa8Q19dS8zgmAdYF7LD6M+fIhK jQASXgoaMXxlFDFKVVpY5JwqnkMfW70jdX9TbIEPkJEkqRYbPOPz8dJdvRmEWA== Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (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 did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4TDwWN3hGgzpVk; Tue, 16 Jan 2024 17:10:40 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.17.1/8.17.1) with ESMTP id 40GHAeES015095; Tue, 16 Jan 2024 17:10:40 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.17.1/8.17.1/Submit) id 40GHAe3x015092; Tue, 16 Jan 2024 17:10:40 GMT (envelope-from git) Date: Tue, 16 Jan 2024 17:10:40 GMT Message-Id: <202401161710.40GHAe3x015092@gitrepo.freebsd.org> To: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org From: Emmanuel Vadot Subject: git: 62bb32d7090f - main - security/vuxml: Document xorg-server and xwayland recent vulnerabilities List-Id: Commit messages for all branches of the ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-all@freebsd.org X-BeenThere: dev-commits-ports-all@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: manu X-Git-Repository: ports X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 62bb32d7090f238f26fad34e71e7c37f8557deae Auto-Submitted: auto-generated The branch main has been updated by manu: URL: https://cgit.FreeBSD.org/ports/commit/?id=62bb32d7090f238f26fad34e71e7c37f8557deae commit 62bb32d7090f238f26fad34e71e7c37f8557deae Author: Emmanuel Vadot AuthorDate: 2024-01-16 17:09:39 +0000 Commit: Emmanuel Vadot CommitDate: 2024-01-16 17:09:39 +0000 security/vuxml: Document xorg-server and xwayland recent vulnerabilities Sponsored by: Beckhoff Automation GmbH & Co. KG --- security/vuxml/vuln/2024.xml | 80 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) diff --git a/security/vuxml/vuln/2024.xml b/security/vuxml/vuln/2024.xml index 6a87603e946c..b8422dcf2b6c 100644 --- a/security/vuxml/vuln/2024.xml +++ b/security/vuxml/vuln/2024.xml @@ -1,3 +1,83 @@ + + xorg server -- Multiple vulnerabilities + + + xorg-server + xephyr + xorg-vfbserver + 21.1.11,1 + + + xorg-nextserver + 21.1.11,2 + + + xwayland + 23.2.4 + + + + +

The X.Org project reports:

+
+
    +
  • CVE-2023-6816: Heap buffer overflow in DeviceFocusEvent + and ProcXIQueryPointer + +

    Both DeviceFocusEvent and the XIQueryPointer reply contain a bit + for each logical button currently down. Buttons can be arbitrarily + mapped to any value up to 255 but the X.Org Server was only + allocating space for the device's number of buttons, + leading to a heap overflow if a bigger value was used.

    • +
  • CVE-2024-0229: Reattaching to different master device may lead + to out-of-bounds memory access + +

    If a device has both a button class and a key class and + numButtons is zero, we can get an out-of-bounds write due + to event under-allocation in the DeliverStateNotifyEvent + function.

    • + +
  • CVE-2024-21885: Heap buffer overflow in + XISendDeviceHierarchyEvent + +

    The XISendDeviceHierarchyEvent() function allocates space to + store up to MAXDEVICES (256) xXIHierarchyInfo structures in info. + If a device with a given ID was removed and a new device with + the same ID added both in the same operation, + the single device ID will lead to two info structures being + written to info. + Since this case can occur for every device ID at once, + a total of two times MAXDEVICES info structures might be written + to the allocation, leading to a heap buffer overflow.

    • + +
  • CVE-2024-21886: Heap buffer overflow in DisableDevice + +

    The DisableDevice() function is called whenever an enabled device + is disabled and it moves the device from the inputInfo.devices + linked list to the inputInfo.off_devices linked list. + However, its link/unlink operation has an issue during the recursive + call to DisableDevice() due to the prev pointer pointing to a + removed device. + This issue leads to a length mismatch between the total number of + devices and the number of device in the list, leading to a heap + overflow and, possibly, to local privilege escalation.

    • +
+
+ + + + CVE-2023-6816 + CVE-2024-0229 + CVE-2024-21885 + CVE-2024-21886 + https://lists.x.org/archives/xorg/2024-January/061525.html + + + 2024-01-16 + 2024-01-16 + + + electron{26,27} -- multiple vulnerabilities