From: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
To: ohilyard@iol.unh.edu
Cc: dev@dpdk.org, david.marchand@redhat.com,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH] lib/rte_rib6: fix stack buffer overflow
Date: Wed, 16 Jun 2021 20:27:41 +0300 [thread overview]
Message-ID: <983355ce-f2f7-ecc0-45be-9dad64ab979f@intel.com> (raw)
In-Reply-To: <20210616095632.0f97eeb3@hermes.local>
Hi Owen,
Thanks for the fix.
I like your solution with removing the loop. However, while this fixes
the buffer overflow, IMO it is not complete, because get_dir() shouldn't
be called in cases where depth = 128. In this case checking the MSB of
the ip is not quite right thing.
The only place where it is possible (depth == 128) is on calling
get_nxt_node() from rte_rib6_lookup(), so I would suggest adding
something like this:
if (depth == 128)
return NULL;
to get_nxt_node() along with your changes.
Also, apart from Stephen's comments, please add the corresponding
fixline to the v2.
Thanks!
On 16/06/2021 19:56, Stephen Hemminger wrote:
> On Wed, 16 Jun 2021 12:07:29 -0400
> ohilyard@iol.unh.edu wrote:
>
>> From: Owen Hilyard <ohilyard@iol.unh.edu>
>>
>> ASAN found a stack buffer overflow in lib/rib/rte_rib6.c:get_dir.
>> The fix for the stack buffer overflow was to make sure depth
>> was always < 128, since when depth = 128 it caused the index
>> into the ip address to be 16, which read off the end of the array.
>>
>> While trying to solve the buffer overflow, I noticed that a few
>> changes could be made to remove the for loop entirely.
>>
>> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
>> ---
>> lib/rib/rte_rib6.c | 22 ++++++++++++++--------
>> 1 file changed, 14 insertions(+), 8 deletions(-)
>>
>> diff --git a/lib/rib/rte_rib6.c b/lib/rib/rte_rib6.c
>> index f6c55ee45..2de50449d 100644
>> --- a/lib/rib/rte_rib6.c
>> +++ b/lib/rib/rte_rib6.c
>> @@ -79,14 +79,20 @@ is_covered(const uint8_t ip1[RTE_RIB6_IPV6_ADDR_SIZE],
>> static inline int
>> get_dir(const uint8_t ip[RTE_RIB6_IPV6_ADDR_SIZE], uint8_t depth)
>> {
>> - int i = 0;
>> - uint8_t p_depth, msk;
>> -
>> - for (p_depth = depth; p_depth >= 8; p_depth -= 8)
>> - i++;
>> -
>> - msk = 1 << (7 - p_depth);
>> - return (ip[i] & msk) != 0;
>> + int index, msk;
>> + /* depth & 127 clamps depth to values that will not
>
> Please put blank line after declarations for clarity.
> Since index and mask are not signed values, please make them unsigned.
> Better yet, make them sized to the appropriate number of bits.
>
>> + * read off the end of ip.
>> + * depth is the number of bits deep into ip to traverse, and
>> + * is incremented in blocks of 8 (1 byte). This means the last
>> + * 3 bits are irrelevant to what the index of ip should be.
>> + */
>> + index = (depth & 127) >> 3;
>> + /*
>> + * msk is the bitmask used to extract the bit used to decide the
>> + * direction of the next step of the binary search.
>> + */
>> + msk = 1 << (7 - (depth & 7));
>> + return (ip[index] & msk) != 0;
>> }
>>
>> static inline struct rte_rib6_node *
>
--
Regards,
Vladimir
next prev parent reply other threads:[~2021-06-16 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 16:07 ohilyard
2021-06-16 16:56 ` Stephen Hemminger
2021-06-16 17:27 ` Medvedkin, Vladimir [this message]
2021-06-16 18:18 ` [dpdk-dev] [PATCH v2] " ohilyard
2021-06-18 16:22 ` Medvedkin, Vladimir
2021-06-18 16:27 ` Medvedkin, Vladimir
2021-06-21 13:28 ` [dpdk-dev] [PATCH v3] " ohilyard
2021-06-22 7:10 ` David Marchand
2021-06-22 10:51 ` Medvedkin, Vladimir
2021-06-23 15:17 ` [dpdk-dev] [PATCH v4] rib: fix max depth IPv6 lookup ohilyard
2021-06-24 13:23 ` David Marchand
2021-06-24 9:01 ` [dpdk-dev] [PATCH v3] lib/rte_rib6: fix stack buffer overflow Medvedkin, Vladimir
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=983355ce-f2f7-ecc0-45be-9dad64ab979f@intel.com \
--to=vladimir.medvedkin@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ohilyard@iol.unh.edu \
--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).