wireguard: dont stacksmash bad peer base64 keys
Just like commit 252647482b24bb3474e8f13bc86100718176832f
did for Wireguard interface keys, prevent stack smashing
the peer keys.
Integer math on 32 bytes of base64 data might yield 33 bytes
of data in some poorly formed user input of private key values.
Rather than smashing the stack (detected) and aborting, simply
allow for the possible yet irrelevant 33-rd byte of data.
Type: fix
Fixes: edca1325cf
Signed-off-by: Jon Loeliger <jdl@netgate.com>
Change-Id: I9f77b3faaaa01d3123b356c958db60c87238db9c
This commit is contained in:

committed by
Matthew Smith

parent
f479179598
commit
d23c55fa56
@ -162,7 +162,7 @@ wg_peer_add_command_fn (vlib_main_t * vm,
|
||||
unformat_input_t _line_input, *line_input = &_line_input;
|
||||
|
||||
u8 *public_key_64 = 0;
|
||||
u8 public_key[NOISE_PUBLIC_KEY_LEN];
|
||||
u8 public_key[NOISE_PUBLIC_KEY_LEN + 1];
|
||||
fib_prefix_t allowed_ip, *allowed_ips = NULL;
|
||||
ip_prefix_t pfx;
|
||||
ip_address_t ip;
|
||||
|
Reference in New Issue
Block a user