From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EF05F194139; Thu, 1 Aug 2024 00:30:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1722472222; cv=none; b=DenQPdgVYACgMB1rVs7pheQ2iVnRwhbWxGlHw5ygp0lzxnpgc1AKY8zaBnDG/T+y6bX0jzjO4R6qNUdRbpIui3cZeT9o+pdJjlzzLpGYka78tobrLHtxhzHML5DqlIgAfBvpQPGBFC4Nlrq3BJbVMN4/BNA6cP3SFCbmq3J2nCw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1722472222; c=relaxed/simple; bh=oM/X7u292WynIc0c7dCQAPziPZvIVDKUQaLBaEsICFI=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=bKdQOPo677KabXrcsOorCjreCox7HYNGrEkmhCG9jDFhgti1sByfvAp014IgbKdNRWyYKGP8S06UG2ely2pB2htL/uuQYF8ZBgRBbfO/OBIU2GFFrZuggIBjVeHo1lWPMMA/4dwbmqbOUjWqq+pRpAuFgfJspa0jzaxTEf10J6M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=CSdW/yYa; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="CSdW/yYa" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8EAD2C116B1; Thu, 1 Aug 2024 00:30:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1722472221; bh=oM/X7u292WynIc0c7dCQAPziPZvIVDKUQaLBaEsICFI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=CSdW/yYaDw8+pQOKb7qGNSJKG7tOuJJ51OeF9L+rRxfjsphoeTOTIDY5KUjm33iF+ N3TeDTDF79qEEzL30T5oqRER4zo/wSTe3yWSFrsX9lYogeS8d55c9hV4HWUW7jiqJG XLJKrx5Q+JX6B/EdcMN1K1mThCsK3N17oAZxnvrXeKLP/ThHticGxNETgWotAPAaSC GdGJIAHn5cD0OtrB6xdLibg62zwTP/r4Z5wOrCooUJ/xyySj4yXzqz0X/RSInzYUAc QbcZ7HQkqzFiBvyzHjO2SBj8P07mWxpv2xjk+bNfvFX8jdYUGeX0GXTcNfETQr1J5L DpHwGpzFHjiRw== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Casey Schaufler , Konstantin Andreev , Sasha Levin , paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com, linux-security-module@vger.kernel.org Subject: [PATCH AUTOSEL 6.1 34/61] smack: tcp: ipv4, fix incorrect labeling Date: Wed, 31 Jul 2024 20:25:52 -0400 Message-ID: <20240801002803.3935985-34-sashal@kernel.org> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240801002803.3935985-1-sashal@kernel.org> References: <20240801002803.3935985-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: linux-security-module@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 6.1.102 Content-Transfer-Encoding: 8bit From: Casey Schaufler [ Upstream commit 2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550 ] Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write. Here is a scenario how to see this: * Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment) * At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections * From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works. * Send some data in both directions. * Collect network traffic of this connection. All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided. I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims. Signed-off-by: Konstantin Andreev Signed-off-by: Casey Schaufler Signed-off-by: Sasha Levin --- security/smack/smack_lsm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/security/smack/smack_lsm.c b/security/smack/smack_lsm.c index b0a483e40c827..75b3e91d5a5f8 100644 --- a/security/smack/smack_lsm.c +++ b/security/smack/smack_lsm.c @@ -4290,7 +4290,7 @@ static int smack_inet_conn_request(const struct sock *sk, struct sk_buff *skb, rcu_read_unlock(); if (hskp == NULL) - rc = netlbl_req_setattr(req, &skp->smk_netlabel); + rc = netlbl_req_setattr(req, &ssp->smk_out->smk_netlabel); else netlbl_req_delattr(req); -- 2.43.0