diff options
| author | Florian Westphal <fw@strlen.de> | 2016-04-01 14:17:21 +0200 |
|---|---|---|
| committer | Sasha Levin <sasha.levin@oracle.com> | 2016-07-10 23:07:32 -0400 |
| commit | cf756388f8f34e02a338356b3685c46938139871 (patch) | |
| tree | bc466e005c0391a306df45dc7c48f2371c48dede /Documentation/static-keys.txt | |
| parent | 850c377e0e2d76723884d610ff40827d26aa21eb (diff) | |
netfilter: x_tables: don't move to non-existent next rule
[ Upstream commit f24e230d257af1ad7476c6e81a8dc3127a74204e ]
Ben Hawkes says:
In the mark_source_chains function (net/ipv4/netfilter/ip_tables.c) it
is possible for a user-supplied ipt_entry structure to have a large
next_offset field. This field is not bounds checked prior to writing a
counter value at the supplied offset.
Base chains enforce absolute verdict.
User defined chains are supposed to end with an unconditional return,
xtables userspace adds them automatically.
But if such return is missing we will move to non-existent next rule.
Reported-by: Ben Hawkes <hawkes@google.com>
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Diffstat (limited to 'Documentation/static-keys.txt')
0 files changed, 0 insertions, 0 deletions