lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <710c74d0-61f8-a1ae-e979-4143f26dfe75@gmail.com>
Date:   Thu, 8 Oct 2020 16:32:37 +0200
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Florent Fourcot <florent.fourcot@...irst.fr>,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next] neigh: add netlink filtering based on LLADDR for
 dump



On 10/8/20 12:59 PM, Florent Fourcot wrote:
> neighbours table dump supports today two filtering:
>  * based on interface index
>  * based on master index
> 
> This patch adds a new filtering, based on layer two address. That will
> help to replace something like it:
> 
>  ip neigh show | grep aa:11:22:bb:ee:ff
> 
> by a better command:
> 
>  ip neigh show lladdr aa:11:22:bb:ee:ff
> 
> Signed-off-by: Florent Fourcot <florent.fourcot@...irst.fr>
> ---
>  net/core/neighbour.c | 24 ++++++++++++++++++++++--
>  1 file changed, 22 insertions(+), 2 deletions(-)
> 
> diff --git a/net/core/neighbour.c b/net/core/neighbour.c
> index 8e39e28b0a8d..4b32bf49a005 100644
> --- a/net/core/neighbour.c
> +++ b/net/core/neighbour.c
> @@ -2542,9 +2542,25 @@ static bool neigh_ifindex_filtered(struct net_device *dev, int filter_idx)
>  	return false;
>  }
>  
> +static bool neigh_lladdr_filtered(struct neighbour *neigh, const u8 *lladdr)
> +{
> +	if (!lladdr)
> +		return false;
> +
> +	/* Ignore all empty values when lladdr filtering is set */
> +	if (!neigh->dev->addr_len)
> +		return true;
> +
> +	if (memcmp(lladdr, neigh->ha, neigh->dev->addr_len) != 0)

Where do you check that lladdr contains exactly neigh->dev->addr_len bytes ?

> +		return true;
> +
> +	return false;
> +}
> +
>  struct neigh_dump_filter {
>  	int master_idx;
>  	int dev_idx;
> +	void *lladdr;
>  };
>  
>  static int neigh_dump_table(struct neigh_table *tbl, struct sk_buff *skb,
> @@ -2558,7 +2574,7 @@ static int neigh_dump_table(struct neigh_table *tbl, struct sk_buff *skb,
>  	struct neigh_hash_table *nht;
>  	unsigned int flags = NLM_F_MULTI;
>  
> -	if (filter->dev_idx || filter->master_idx)
> +	if (filter->dev_idx || filter->master_idx || filter->lladdr)
>  		flags |= NLM_F_DUMP_FILTERED;
>  
>  	rcu_read_lock_bh();
> @@ -2573,7 +2589,8 @@ static int neigh_dump_table(struct neigh_table *tbl, struct sk_buff *skb,
>  			if (idx < s_idx || !net_eq(dev_net(n->dev), net))
>  				goto next;
>  			if (neigh_ifindex_filtered(n->dev, filter->dev_idx) ||
> -			    neigh_master_filtered(n->dev, filter->master_idx))
> +			    neigh_master_filtered(n->dev, filter->master_idx) ||
> +			    neigh_lladdr_filtered(n, filter->lladdr))
>  				goto next;
>  			if (neigh_fill_info(skb, n, NETLINK_CB(cb->skb).portid,
>  					    cb->nlh->nlmsg_seq,
> @@ -2689,6 +2706,9 @@ static int neigh_valid_dump_req(const struct nlmsghdr *nlh,
>  		case NDA_MASTER:
>  			filter->master_idx = nla_get_u32(tb[i]);
>  			break;
> +		case NDA_LLADDR:
> +			filter->lladdr = nla_data(tb[i]);

This comes from user space, and could contains an arbitrary amount of bytes, like 0 byte.

You probably have to store the full attribute, so that you can use nla_len() and nla_data()

> +			break;
>  		default:
>  			if (strict_check) {
>  				NL_SET_ERR_MSG(extack, "Unsupported attribute in neighbor dump request");
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ