All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olga Kornievskaia <kolga@netapp.com>
To: <steved@redhat.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: [PATCH 1/1] nfs-utils: Add check of clientaddr argument
Date: Thu, 24 May 2018 16:05:42 -0400	[thread overview]
Message-ID: <20180524200542.22685-1-kolga@netapp.com> (raw)

If the user supplies a clientaddr value, it should be either
a special value of either IPV4/IPV6 any address or a local address
on the same network that the server being mounted. Otherwise, we
disallow the client to use an arbitrary value of the clientaddr value.
This value is used to construct a client id of SETCLIENTID and
providing a false value can interfere with the real owner's mount.

Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
---
 utils/mount/stropts.c | 24 ++++++++++++++++++++----
 1 file changed, 20 insertions(+), 4 deletions(-)

diff --git a/utils/mount/stropts.c b/utils/mount/stropts.c
index d1b0708..44a6ff5 100644
--- a/utils/mount/stropts.c
+++ b/utils/mount/stropts.c
@@ -229,7 +229,8 @@ static int nfs_append_addr_option(const struct sockaddr *sap,
 
 /*
  * Called to discover our address and append an appropriate 'clientaddr='
- * option to the options string.
+ * option to the options string. If the supplied 'clientaddr=' value does
+ * not match either IPV4/IPv6 any or a local address, then fail the mount.
  *
  * Returns 1 if 'clientaddr=' option created successfully or if
  * 'clientaddr=' option is already present; otherwise zero.
@@ -242,11 +243,26 @@ static int nfs_append_clientaddr_option(const struct sockaddr *sap,
 	struct sockaddr *my_addr = &address.sa;
 	socklen_t my_len = sizeof(address);
 
-	if (po_contains(options, "clientaddr") == PO_FOUND)
-		return 1;
-
 	nfs_callback_address(sap, salen, my_addr, &my_len);
 
+	if (po_contains(options, "clientaddr") == PO_FOUND) {
+		char *addr = po_get(options, "clientaddr");
+		char address[NI_MAXHOST];
+
+		if (!strcmp(addr, "0.0.0.0") || !strcmp(addr, "::"))
+			return 1;
+		if (!nfs_present_sockaddr(my_addr, my_len, address,
+						sizeof(address)))
+			goto out;
+
+		if (strcmp(addr, address)) {
+			nfs_error(_("%s: failed to validate clientaddr "
+					"address"), progname);
+			return 0;
+		}
+		return 1;
+	}
+out:
 	return nfs_append_generic_address_option(my_addr, my_len,
 							"clientaddr", options);
 }
-- 
1.8.3.1


             reply	other threads:[~2018-05-24 20:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 20:05 Olga Kornievskaia [this message]
2018-05-25  0:50 ` [PATCH 1/1] nfs-utils: Add check of clientaddr argument Chuck Lever
2018-05-25 14:02   ` Olga Kornievskaia
2018-05-25 16:24     ` Chuck Lever
2018-05-25 16:44       ` Olga Kornievskaia
2018-05-25 16:47         ` Olga Kornievskaia
2018-05-25 17:05           ` Chuck Lever
2018-05-25 17:14             ` Olga Kornievskaia
2018-05-25 17:04         ` Chuck Lever
2018-05-25 22:35           ` Chuck Lever
2018-05-29 20:07             ` Olga Kornievskaia
2018-05-29 20:53               ` Chuck Lever
2018-06-01 21:42                 ` Chuck Lever
2018-06-02 13:37                   ` Olga Kornievskaia
2018-06-02 16:34                     ` Chuck Lever
  -- strict thread matches above, loose matches on Subject: below --
2018-05-24 20:03 Olga Kornievskaia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180524200542.22685-1-kolga@netapp.com \
    --to=kolga@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.