* [Qemu-devel] [PATCH] Limit memory r/w length to buffer size
@ 2015-10-12 19:31 P J P
2015-10-13 18:29 ` P J P
2015-10-13 18:58 ` Markus Armbruster
0 siblings, 2 replies; 4+ messages in thread
From: P J P @ 2015-10-12 19:31 UTC (permalink / raw)
To: qemu-devel; +Cc: Gerben van der Lubbe
Hello,
An OOB r/w access issue was reported by Mr Gerben Lubbe(CC'd here).
The GDB(1) stub protocol supports commands 'm/M' to read & write 'len' bytes
from/to the stub memory area. In that, the 'len' parameter value supplied by
the host gdb(1) is not validated against the local buffer size. Which in turn
could lead to OOB r/w memory access.
Below is a proposed patch to fix this issue.
===
>From 88edb457a66f8ff96209a1603914171eade0658b Mon Sep 17 00:00:00 2001
From: Prasad J Pandit <pjp@fedoraproject.org>
Date: Mon, 12 Oct 2015 22:56:41 +0530
Subject: Limit memory r/w length to buffer size
GDB(1) stub communication protocol supports commands m/M to read
and write 'len' bytes from/to the stub memory area.
m addr,len : read 'len' bytes from address 'addr'
M addr,len:<data> : write 'len' bytes of 'data' to 'addr'
Qemu stub uses automatic buffers of size 'MAX_PACKET_LENGTH=4096'
to process these commands. Limit 'len' parameter value supplied
by the host gdb(1) to the maximum buffer size to avoid any OOB
buffer access.
Reported-by: Gerben van der Lubbe <spoofedexistence@gmail.com>
Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
---
gdbstub.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gdbstub.c b/gdbstub.c
index ffe7e6e..39da736 100644
--- a/gdbstub.c
+++ b/gdbstub.c
@@ -956,6 +956,7 @@ static int gdb_handle_packet(GDBState *s, const char *line_buf)
if (*p == ',')
p++;
len = strtoull(p, NULL, 16);
+ len = len > MAX_PACKET_LENGTH ? MAX_PACKET_LENGTH : len;
if (target_memory_rw_debug(s->g_cpu, addr, mem_buf, len, false) != 0) {
put_packet (s, "E14");
} else {
@@ -968,6 +969,7 @@ static int gdb_handle_packet(GDBState *s, const char *line_buf)
if (*p == ',')
p++;
len = strtoull(p, (char **)&p, 16);
+ len = len > MAX_PACKET_LENGTH ? MAX_PACKET_LENGTH : len;
if (*p == ':')
p++;
hextomem(mem_buf, p, len);
--
2.4.3
===
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [Qemu-devel] [PATCH] Limit memory r/w length to buffer size
2015-10-12 19:31 [Qemu-devel] [PATCH] Limit memory r/w length to buffer size P J P
@ 2015-10-13 18:29 ` P J P
2015-10-13 18:58 ` Markus Armbruster
1 sibling, 0 replies; 4+ messages in thread
From: P J P @ 2015-10-13 18:29 UTC (permalink / raw)
To: qemu-devel; +Cc: Gerben van der Lubbe
Hello,
+-- On Tue, 13 Oct 2015, P J P wrote --+
| Below is a proposed patch to fix this issue.
|
| ===
| > From 88edb457a66f8ff96209a1603914171eade0658b Mon Sep 17 00:00:00 2001
| From: Prasad J Pandit <pjp@fedoraproject.org>
| Date: Mon, 12 Oct 2015 22:56:41 +0530
| Subject: Limit memory r/w length to buffer size
|
| GDB(1) stub communication protocol supports commands m/M to read
| and write 'len' bytes from/to the stub memory area.
|
| m addr,len : read 'len' bytes from address 'addr'
| M addr,len:<data> : write 'len' bytes of 'data' to 'addr'
|
| Qemu stub uses automatic buffers of size 'MAX_PACKET_LENGTH=4096'
| to process these commands. Limit 'len' parameter value supplied
| by the host gdb(1) to the maximum buffer size to avoid any OOB
| buffer access.
|
| Reported-by: Gerben van der Lubbe <spoofedexistence@gmail.com>
| Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
| ---
| gdbstub.c | 2 ++
| 1 file changed, 2 insertions(+)
Could someone review it please?
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] [PATCH] Limit memory r/w length to buffer size
2015-10-12 19:31 [Qemu-devel] [PATCH] Limit memory r/w length to buffer size P J P
2015-10-13 18:29 ` P J P
@ 2015-10-13 18:58 ` Markus Armbruster
2015-10-14 6:27 ` P J P
1 sibling, 1 reply; 4+ messages in thread
From: Markus Armbruster @ 2015-10-13 18:58 UTC (permalink / raw)
To: P J P; +Cc: Kevin Wolf, Gerben van der Lubbe, qemu-devel
P J P <ppandit@redhat.com> writes:
> Hello,
>
> An OOB r/w access issue was reported by Mr Gerben Lubbe(CC'd here).
>
> The GDB(1) stub protocol supports commands 'm/M' to read & write 'len'
> bytes from/to the stub memory area. In that, the 'len' parameter value
> supplied by the host gdb(1) is not validated against the local buffer
> size. Which in turn could lead to OOB r/w memory access.
>
> Below is a proposed patch to fix this issue.
How is this related to Kevin's
[PATCH] gdbstub: Fix buffer overflows in gdb_handle_packet()
Message-Id: <1444721930-5121-1-git-send-email-kwolf@redhat.com>
?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] [PATCH] Limit memory r/w length to buffer size
2015-10-13 18:58 ` Markus Armbruster
@ 2015-10-14 6:27 ` P J P
0 siblings, 0 replies; 4+ messages in thread
From: P J P @ 2015-10-14 6:27 UTC (permalink / raw)
To: Markus Armbruster; +Cc: Kevin Wolf, Gerben van der Lubbe, qemu-devel
+-- On Tue, 13 Oct 2015, Markus Armbruster wrote --+
| How is this related to Kevin's
| [PATCH] gdbstub: Fix buffer overflows in gdb_handle_packet()
| Message-Id: <1444721930-5121-1-git-send-email-kwolf@redhat.com> ?
Oh, didn't know there was already a patch. Yes it fixes the same issues;
Also the length check is correct. In my patch I did not consider the size
alterations that occur in memtohex() & hextomem().
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-10-14 6:28 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-10-12 19:31 [Qemu-devel] [PATCH] Limit memory r/w length to buffer size P J P
2015-10-13 18:29 ` P J P
2015-10-13 18:58 ` Markus Armbruster
2015-10-14 6:27 ` P J P
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).