public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
* [PATCH] Fix buffer overrun in fetch_register_using_p
@ 2018-10-10 15:46 Richard Henderson
  2018-10-10 20:38 ` Simon Marchi
  0 siblings, 1 reply; 2+ messages in thread
From: Richard Henderson @ 2018-10-10 15:46 UTC (permalink / raw)
  To: gdb-patches

If the packet returned from the gdbserver is too long,
the stack would be clobbered and gdb would crash.

gdb/
	* remote.c (remote_target::fetch_register_using_p): Error if
	more data is received than expected in the packet.
---

I am adding SVE support to QEMU's gdbserver stub, and managed to
tickle this bug in the process.


r~

---
 gdb/remote.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/gdb/remote.c b/gdb/remote.c
index 724f41cf71..d68faf1046 100644
--- a/gdb/remote.c
+++ b/gdb/remote.c
@@ -7958,7 +7958,8 @@ remote_target::fetch_register_using_p (struct regcache *regcache,
   struct gdbarch *gdbarch = regcache->arch ();
   struct remote_state *rs = get_remote_state ();
   char *buf, *p;
-  gdb_byte *regp = (gdb_byte *) alloca (register_size (gdbarch, reg->regnum));
+  int size = register_size (gdbarch, reg->regnum);
+  gdb_byte *regp = (gdb_byte *) alloca (size);
   int i;
 
   if (packet_support (PACKET_p) == PACKET_DISABLE)
@@ -8003,6 +8004,8 @@ remote_target::fetch_register_using_p (struct regcache *regcache,
     {
       if (p[1] == 0)
 	error (_("fetch_register_using_p: early buf termination"));
+      if (i == size)
+	error (_("fetch_register_using_p: late buf termination"));
 
       regp[i++] = fromhex (p[0]) * 16 + fromhex (p[1]);
       p += 2;
-- 
2.17.1

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH] Fix buffer overrun in fetch_register_using_p
  2018-10-10 15:46 [PATCH] Fix buffer overrun in fetch_register_using_p Richard Henderson
@ 2018-10-10 20:38 ` Simon Marchi
  0 siblings, 0 replies; 2+ messages in thread
From: Simon Marchi @ 2018-10-10 20:38 UTC (permalink / raw)
  To: Richard Henderson; +Cc: gdb-patches

On 2018-10-10 11:45, Richard Henderson wrote:
> If the packet returned from the gdbserver is too long,
> the stack would be clobbered and gdb would crash.
> 
> gdb/
> 	* remote.c (remote_target::fetch_register_using_p): Error if
> 	more data is received than expected in the packet.
> ---
> 
> I am adding SVE support to QEMU's gdbserver stub, and managed to
> tickle this bug in the process.
> 
> 
> r~
> 
> ---
>  gdb/remote.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/gdb/remote.c b/gdb/remote.c
> index 724f41cf71..d68faf1046 100644
> --- a/gdb/remote.c
> +++ b/gdb/remote.c
> @@ -7958,7 +7958,8 @@ remote_target::fetch_register_using_p (struct
> regcache *regcache,
>    struct gdbarch *gdbarch = regcache->arch ();
>    struct remote_state *rs = get_remote_state ();
>    char *buf, *p;
> -  gdb_byte *regp = (gdb_byte *) alloca (register_size (gdbarch, 
> reg->regnum));
> +  int size = register_size (gdbarch, reg->regnum);
> +  gdb_byte *regp = (gdb_byte *) alloca (size);
>    int i;
> 
>    if (packet_support (PACKET_p) == PACKET_DISABLE)
> @@ -8003,6 +8004,8 @@ remote_target::fetch_register_using_p (struct
> regcache *regcache,
>      {
>        if (p[1] == 0)
>  	error (_("fetch_register_using_p: early buf termination"));
> +      if (i == size)
> +	error (_("fetch_register_using_p: late buf termination"));

Hi Richard,

As a user, I don't think I would understand "late buf termination".  I 
think it could be more straightforward, like "the received value is 
larger than the register size".

Otherwise, this is OK, thanks for this.

Simon

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-10-10 20:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-10 15:46 [PATCH] Fix buffer overrun in fetch_register_using_p Richard Henderson
2018-10-10 20:38 ` Simon Marchi

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 read-only IMAP folder(s) and NNTP newsgroup(s).