From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/4] Test for CVE-2016-4997 on setsockopt
Date: Mon, 27 Mar 2017 17:34:40 +0200 [thread overview]
Message-ID: <20170327153439.GD21272@rei.lan> (raw)
In-Reply-To: <20170323162633.7e49c7ae@linux-v3j5>
Hi!
> +static void run(void)
> +{
> + int ret, sock_fd;
> + struct payload p = { 0 };
> +
> + sock_fd = SAFE_SOCKET(AF_INET, SOCK_DGRAM, 0);
> +
> + strncpy(p.match.u.user.name, "icmp", sizeof(p.match.u.user.name));
> + p.match.u.match_size = OFFSET_OVERWRITE;
> +
> + p.ent.next_offset = NEXT_OFFSET;
> + p.ent.target_offset = TOO_SMALL_OFFSET;
> +
> + p.repl.num_entries = 2;
> + p.repl.num_counters = 1;
> + p.repl.size = sizeof(struct payload);
> + p.repl.valid_hooks = 0;
> +
> + ret = setsockopt(sock_fd, SOL_IP, IPT_SO_SET_REPLACE,
> + &p, sizeof(struct payload));
> + tst_res(TPASS | TERRNO, "We didn't cause a crash, setsockopt returned %d", ret);
> + if (sizeof(long) > 4)
> + tst_res(TCONF,
> + "The original vulnerability was only present in 32-bit compat mode");
Why do we issue the TCONF at the end of the test? Shouldn't this be
something do in the test setup?
Also we have tst_kernel_bits() in the test library, so we can do
something as:
if (tst_kernel_bits() == 32 || sizeof(long) > 4)
tst_res(TCONF, "...");
> +}
> +
> +static struct tst_test test = {
> + .tid = "cve-2016-4997",
> + .min_kver = "2.6.32",
> + .test_all = run,
> + .needs_root = 1,
> +};
I also wonder if we should compile the test with -m32 by default, we
whould have to add a configure test if compilation with -m32 works
though.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-03-27 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 15:26 [LTP] [PATCH 2/4] Test for CVE-2016-4997 on setsockopt Richard Palethorpe
2017-03-27 15:34 ` Cyril Hrubis [this message]
2017-03-27 16:08 ` Richard Palethorpe
2017-03-28 8:27 ` Cyril Hrubis
2017-03-28 9:39 ` Cyril Hrubis
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=20170327153439.GD21272@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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