[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANhBUQ0KD9YqYWT-m7q-7FcqAwRstVPzh_s2rRmCCjwQYcivBQ@mail.gmail.com>
Date: Mon, 5 Aug 2019 14:22:38 +0800
From: Chuhong Yuan <hslester96@...il.com>
To: James Bottomley <jejb@...ux.ibm.com>
Cc: Adam Radford <aradford@...il.com>,
"Martin K . Petersen" <martin.petersen@...cle.com>,
linux-scsi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] scsi: 3w-sas: Fix unterminated strncpy
On Tue, Jul 30, 2019 at 10:56 PM James Bottomley <jejb@...ux.ibm.com> wrote:
>
> On Tue, 2019-07-30 at 16:40 +0800, Chuhong Yuan wrote:
> > strncpy(dest, src, strlen(src)) leads to unterminated
> > dest, which is dangerous.
>
> I don't buy that. The structure is only used for the
> TW_IOCTL_GET_COMPATIBILITY_INFO ioctl and all the fields for that are
> fixed width and are copied over as such.
>
> > Here driver_version's len is 32 and TW_DRIVER_VERSION
> > is shorter than 32.
> > Therefore strcpy is OK.
>
> The best practice for copying a string to a fixed width destination
> that does get printed within the kernel would be what the 3w-9xxx.c
> does
>
> strlcpy(tw_dev->tw_compat_info.driver_version, TW_DRIVER_VERSION,
> sizeof(tw_dev->tw_compat_info.driver_version));
>
This is right, and strscpy() is better than strlcpy(). strlcpy() is deprecated
now according to the documentation.
I choose strcpy() since it has better performance and there is no worry of
overflow here. And I find there are indeed some places using strcpy() to fix
this problem, like add_man_viewer() in tools/perf/builtin-help.c.
> But as I said, it doesn't really matter for a fixed width field that's
> never printed within the kernel.
>
I think it is not good to leave a exploitable place here, and fixing it does not
need much effort.
Regards,
Chuhong
> James
>
Powered by blists - more mailing lists