From: walter harms <wharms@bfs.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Karsten Keil <isdn@linux-pingi.de>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch v2] isdn: icn: buffer overflow in icn_command()
Date: Wed, 16 Apr 2014 14:10:07 +0200 [thread overview]
Message-ID: <534E731F.6060701@bfs.de> (raw)
In-Reply-To: <20140416112516.GA12917@mwanda>
Am 16.04.2014 13:25, schrieb Dan Carpenter:
> This buffer over was detected using static analysis:
>
> drivers/isdn/icn/icn.c:1325 icn_command()
> error: format string overflow. buf_size: 60 length: 98
>
> The calculation for the length of the string is off because it assumes
> that the dial[] buffer holds a 50 character string, but actually it is
> at most 31 characters and NUL. I have removed the dial[] buffer because
> it isn't needed.
>
> The maximum length of the string is actually 79 characters and a NUL. I
> have made the cbuf[] array large enough to hold it and changed the
> sprintf() to an snprintf() as a further safety enhancement.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> v2: update changelog.
>
> diff --git a/drivers/isdn/icn/icn.c b/drivers/isdn/icn/icn.c
> index 53d487f..88c0603 100644
> --- a/drivers/isdn/icn/icn.c
> +++ b/drivers/isdn/icn/icn.c
> @@ -1155,7 +1155,7 @@ icn_command(isdn_ctrl *c, icn_card *card)
> ulong a;
> ulong flags;
> int i;
> - char cbuf[60];
> + char cbuf[80];
> isdn_ctrl cmd;
> icn_cdef cdef;
> char __user *arg;
> @@ -1309,7 +1309,6 @@ icn_command(isdn_ctrl *c, icn_card *card)
> break;
> if ((c->arg & 255) < ICN_BCH) {
> char *p;
> - char dial[50];
> char dcode[4];
>
> a = c->arg;
> @@ -1321,10 +1320,10 @@ icn_command(isdn_ctrl *c, icn_card *card)
> } else
> /* Normal Dial */
> strcpy(dcode, "CAL");
> - strcpy(dial, p);
> - sprintf(cbuf, "%02d;D%s_R%s,%02d,%02d,%s\n", (int) (a + 1),
> - dcode, dial, c->parm.setup.si1,
> - c->parm.setup.si2, c->parm.setup.eazmsn);
> + snprintf(cbuf, sizeof(cbuf),
> + "%02d;D%s_R%s,%02d,%02d,%s\n", (int) (a + 1),
> + dcode, p, c->parm.setup.si1,
> + c->parm.setup.si2, c->parm.setup.eazmsn);
> i = icn_writecmd(cbuf, strlen(cbuf), 0, card);
> }
> break;
>
if someone is still working on this ...
maybe a vararg version of icn_writecmd() would be a nice helper.
re,
wh
next prev parent reply other threads:[~2014-04-16 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 8:07 [patch] isdn: icn: buffer overflow in icn_command() Dan Carpenter
2014-04-14 15:52 ` Joe Perches
2014-04-16 11:16 ` Dan Carpenter
2014-04-16 11:47 ` Joe Perches
2014-04-16 11:25 ` [patch v2] " Dan Carpenter
2014-04-16 12:10 ` walter harms [this message]
2014-04-16 19:24 ` David Miller
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=534E731F.6060701@bfs.de \
--to=wharms@bfs.de \
--cc=dan.carpenter@oracle.com \
--cc=isdn@linux-pingi.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.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).