From: Phil Sutter <phil@nwl.cc>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: [iproute PATCH] ip netns: Make sure netns name is sane
Date: Mon, 10 Jul 2017 13:19:12 +0200 [thread overview]
Message-ID: <20170710111912.22537-1-phil@nwl.cc> (raw)
In order to keep track of created netns, 'ip netns' creates a mount
point inside NETNS_RUN_DIR. By not checking the user-specified name, it
allowed to create that mount point outside of NETNS_RUN_DIR and hence
lose track of it afterwards:
| # ip netns add ../../tmp/foobar
| # ip netns list
| # mount | grep foobar
| nsfs on /tmp/foobar type nsfs (rw)
Prevent this by making sure basename() does not see a need to alter the
given netns name.
Fixes: 0dc34c7713bb7 ("iproute2: Add processless network namespace support")
Signed-off-by: Phil Sutter <phil@nwl.cc>
---
ip/ipnetns.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/ip/ipnetns.c b/ip/ipnetns.c
index 0b0378ab6560c..4eee85e146b3d 100644
--- a/ip/ipnetns.c
+++ b/ip/ipnetns.c
@@ -595,6 +595,21 @@ static int create_netns_dir(void)
return 0;
}
+static bool is_basename(const char *name)
+{
+ char *name_dup = strdup(name);
+ bool rc = true;
+
+ if (!name_dup)
+ return false;
+
+ if (strcmp(basename(name_dup), name))
+ rc = false;
+
+ free(name_dup);
+ return rc;
+}
+
static int netns_add(int argc, char **argv)
{
/* This function creates a new network namespace and
@@ -616,6 +631,11 @@ static int netns_add(int argc, char **argv)
}
name = argv[0];
+ if (!is_basename(name)) {
+ fprintf(stderr, "Invalid netns name: contains path components\n");
+ return -1;
+ }
+
snprintf(netns_path, sizeof(netns_path), "%s/%s", NETNS_RUN_DIR, name);
if (create_netns_dir())
--
2.13.1
next reply other threads:[~2017-07-10 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 11:19 Phil Sutter [this message]
2017-07-10 15:17 ` [iproute PATCH] ip netns: Make sure netns name is sane Stephen Hemminger
2017-07-12 12:38 ` Phil Sutter
2017-07-12 16:38 ` Stephen Hemminger
2017-07-12 18:12 ` Phil Sutter
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=20170710111912.22537-1-phil@nwl.cc \
--to=phil@nwl.cc \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).