From nobody Mon Jan 23 12:47:06 2023 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 4P0qcW17tSz3bTgW; Mon, 23 Jan 2023 12:47:07 +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 4P0qcW0X7xz3KXm; Mon, 23 Jan 2023 12:47:07 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1674478027; 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=+ZB2h5EDu0E2ijmIPVa9yBj3aIhuVTYiF2SvJchJZRk=; b=U/oDWb7gMYnL/svsMYReY93OxIjfYn3s4cGr1pJgG1BIJ778+g3lEpGi7ggGp++MyPoPyP AUrQiBdHWEmhokeZ9M0XsYtz/fxfbIrVrSot1ciJrPgN0dxfDmiM8zuUIwk4hV+vRLDzOp 9OTHfyfm+XpskQ5BdkdLvfVSk+awfmEmWjMEbWXg+sK/vyQrF0NvZTvULf9hTHFgGBHpV3 hphZlSI3Kz+XUHh/ePRSCyBz0LdFRYqsqiyiLX1IMrM3D2RoH1dQGzcpJfWOMGO9tYZK5F Kv3yDj0BFdohAs/uN4gSsjJ28JkPylrivoQm2hRuBLzOFm3jxycxAKLQ5V6u3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1674478027; 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=+ZB2h5EDu0E2ijmIPVa9yBj3aIhuVTYiF2SvJchJZRk=; b=uGDvwWG9sh1KCoJFBagNe62RROUFndt1JG3+/k+C1jNJ2Ne9pjIsJpogg95bNxbN+Xifw7 LxiJSs1f3WWbQ4/YgxDmeOMXVpQY9+mkJbiwkG726UMLkSPEoyGfUVEO1tt5EK6RB3RT7d K9Fg/8tT1CQsQ9K5OdsC5RShunCIhRItr9jkRmeXvCoXWVG5mhfpNsM7msfHKDuLWMNeZ6 S6PZ/hXXchJkDmIiqxAV+svy8JFWgs+yOQuntwaFyqBEP8CRl/EQXhC+6VRM6DFGcoQtHt baCYTBeoyorA7wsnJab1eJZ9mVXRu4BCg5kdlGrhQbRRZTuVLe10VLxM/nsGzg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1674478027; a=rsa-sha256; cv=none; b=iVCqMZ+N2YnrF3HTyp3GhHTluKS/YxH2O4dWdNYA5hLb8aLmqx4wQLn9BKk8uFCxTUXTex GjVCwt30HxaanaStwAt3j88PEx2f0OADWdx9JsUfLKmGfedFL9hw1g/SXq1SqnTSFSiCcI 0eFiguXyIfgGYRAVhyCmzjWup7Mo9SorU/3gBJwaACrh8/n7er6hGcXrmx7U73A9yPL6LR 2rZx0HKvCGNoita4Ip4gfXVSWbrknfJc3v3XH05ZU6HhaAzSC70nhjOxpKLIJItuurKKpK HYaCCYTNqlP6QehMnmj7fqnnl6vwoN8S4RSLHiXFver1EMAh2ulAHMVAWL5KFg== 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 4P0qcV6ThMzVMn; Mon, 23 Jan 2023 12:47:06 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 30NCl6mf099460; Mon, 23 Jan 2023 12:47:06 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 30NCl6xN099459; Mon, 23 Jan 2023 12:47:06 GMT (envelope-from git) Date: Mon, 23 Jan 2023 12:47:06 GMT Message-Id: <202301231247.30NCl6xN099459@gitrepo.freebsd.org> To: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org From: =?utf-8?Q?Fernando=20Apestegu=C3=ADa?= Subject: git: 3fb1ffb2b269 - main - security/vuln: Fix file 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: fernape X-Git-Repository: ports X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 3fb1ffb2b26959f4ea21ead0441fe18602cdbfeb Auto-Submitted: auto-generated X-ThisMailContainsUnwantedMimeParts: N The branch main has been updated by fernape: URL: https://cgit.FreeBSD.org/ports/commit/?id=3fb1ffb2b26959f4ea21ead0441fe18602cdbfeb commit 3fb1ffb2b26959f4ea21ead0441fe18602cdbfeb Author: Fernando Apesteguía AuthorDate: 2023-01-23 12:42:21 +0000 Commit: Fernando Apesteguía CommitDate: 2023-01-23 12:42:21 +0000 security/vuln: Fix file It didn't pass `make validate`. --- security/vuxml/vuln/2023.xml | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/security/vuxml/vuln/2023.xml b/security/vuxml/vuln/2023.xml index d43c2aa94ef3..b792812464d5 100644 --- a/security/vuxml/vuln/2023.xml +++ b/security/vuxml/vuln/2023.xml @@ -11,23 +11,23 @@

Peter Ammon reports:

- fish is a command line shell. fish version 3.1.0 through - version 3.3.1 is vulnerable to arbitrary code execution. - git repositories can contain per-repository - configuration that change the behavior of git, including - running arbitrary commands. When using the default - configuration of fish, changing to a directory - automatically runs git commands in order to display - information about the current repository in the prompt. - If an attacker can convince a user to change their - current directory into one controlled by the attacker, - such as on a shared file system or extracted archive, - fish will run arbitrary commands under the attacker's - control. This problem has been fixed in fish 3.4.0. Note - that running git in these directories, including using - the git tab completion, remains a potential trigger for - this issue. As a workaround, remove the - fish_git_prompt function from the prompt. + fish is a command line shell. fish version 3.1.0 through + version 3.3.1 is vulnerable to arbitrary code execution. + git repositories can contain per-repository + configuration that change the behavior of git, including + running arbitrary commands. When using the default + configuration of fish, changing to a directory + automatically runs git commands in order to display + information about the current repository in the prompt. + If an attacker can convince a user to change their + current directory into one controlled by the attacker, + such as on a shared file system or extracted archive, + fish will run arbitrary commands under the attacker's + control. This problem has been fixed in fish 3.4.0. Note + that running git in these directories, including using + the git tab completion, remains a potential trigger for + this issue. As a workaround, remove the + fish_git_prompt function from the prompt.