Out-of-bound write in function parse_command_modifiers in vim/vim
Valid
Reported on
Jun 27th 2022
Description
Out-of-bounds write in function parse_command_modifiers
at ex_docmd.c:3123
Version
commit c101abff4c6756db4f5e740fde289decb9452efa (HEAD -> master, tag: v8.2.5164)
Proof of Concept
guest@elk:~/trung$ ./vim3/src/vim -u NONE -i NONE -n -m -X -Z -e -s -S ./poc/poc4min -c :qa!
=================================================================
==26557==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000007f17 at pc 0x7f58a13e677a bp 0x7ffdcd77a8b0 sp 0x7ffdcd77a058
WRITE of size 7 at 0x602000007f17 thread T0
#0 0x7f58a13e6779 (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x79779)
#1 0x55b4aa3a571d in parse_command_modifiers /home/guest/trung/vim3/src/ex_docmd.c:3123
#2 0x55b4aa39cc28 in do_one_cmd /home/guest/trung/vim3/src/ex_docmd.c:1789
#3 0x55b4aa398b4f in do_cmdline /home/guest/trung/vim3/src/ex_docmd.c:992
#4 0x55b4aa54b7e5 in nv_colon /home/guest/trung/vim3/src/normal.c:3200
#5 0x55b4aa53e53b in normal_cmd /home/guest/trung/vim3/src/normal.c:939
#6 0x55b4aa3c584c in exec_normal /home/guest/trung/vim3/src/ex_docmd.c:8812
#7 0x55b4aa3c5628 in exec_normal_cmd /home/guest/trung/vim3/src/ex_docmd.c:8775
#8 0x55b4aa3c4ec9 in ex_normal /home/guest/trung/vim3/src/ex_docmd.c:8693
#9 0x55b4aa3a17c9 in do_one_cmd /home/guest/trung/vim3/src/ex_docmd.c:2570
#10 0x55b4aa398b4f in do_cmdline /home/guest/trung/vim3/src/ex_docmd.c:992
#11 0x55b4aa6b9b28 in do_source_ext /home/guest/trung/vim3/src/scriptfile.c:1674
#12 0x55b4aa6bac6a in do_source /home/guest/trung/vim3/src/scriptfile.c:1801
#13 0x55b4aa6b77a3 in cmd_source /home/guest/trung/vim3/src/scriptfile.c:1174
#14 0x55b4aa6b7804 in ex_source /home/guest/trung/vim3/src/scriptfile.c:1200
#15 0x55b4aa3a17c9 in do_one_cmd /home/guest/trung/vim3/src/ex_docmd.c:2570
#16 0x55b4aa398b4f in do_cmdline /home/guest/trung/vim3/src/ex_docmd.c:992
#17 0x55b4aa396f4e in do_cmdline_cmd /home/guest/trung/vim3/src/ex_docmd.c:586
#18 0x55b4aa987cc6 in exe_commands /home/guest/trung/vim3/src/main.c:3133
#19 0x55b4aa980ebb in vim_main2 /home/guest/trung/vim3/src/main.c:780
#20 0x55b4aa980777 in main /home/guest/trung/vim3/src/main.c:432
#21 0x7f58a05c9c86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21c86)
#22 0x55b4aa222a99 in _start (/home/guest/trung/vim3/src/vim+0x137a99)
0x602000007f17 is located 0 bytes to the right of 7-byte region [0x602000007f10,0x602000007f17)
allocated by thread T0 here:
#0 0x7f58a144bb40 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb40)
#1 0x55b4aa222edf in lalloc /home/guest/trung/vim3/src/alloc.c:246
#2 0x55b4aa222ce4 in alloc /home/guest/trung/vim3/src/alloc.c:151
#3 0x55b4aa74b7ac in vim_strsave /home/guest/trung/vim3/src/strings.c:27
#4 0x55b4aa3eccf2 in open_cmdwin /home/guest/trung/vim3/src/ex_getln.c:4598
#5 0x55b4aa3e1b76 in getcmdline_int /home/guest/trung/vim3/src/ex_getln.c:1956
#6 0x55b4aa3dfb25 in getcmdline /home/guest/trung/vim3/src/ex_getln.c:1574
#7 0x55b4aa3e5865 in getexline /home/guest/trung/vim3/src/ex_getln.c:2871
#8 0x55b4aa3982dd in do_cmdline /home/guest/trung/vim3/src/ex_docmd.c:875
#9 0x55b4aa54b7e5 in nv_colon /home/guest/trung/vim3/src/normal.c:3200
#10 0x55b4aa53e53b in normal_cmd /home/guest/trung/vim3/src/normal.c:939
#11 0x55b4aa3c584c in exec_normal /home/guest/trung/vim3/src/ex_docmd.c:8812
#12 0x55b4aa3c5628 in exec_normal_cmd /home/guest/trung/vim3/src/ex_docmd.c:8775
#13 0x55b4aa3c4ec9 in ex_normal /home/guest/trung/vim3/src/ex_docmd.c:8693
#14 0x55b4aa3a17c9 in do_one_cmd /home/guest/trung/vim3/src/ex_docmd.c:2570
#15 0x55b4aa398b4f in do_cmdline /home/guest/trung/vim3/src/ex_docmd.c:992
#16 0x55b4aa6b9b28 in do_source_ext /home/guest/trung/vim3/src/scriptfile.c:1674
#17 0x55b4aa6bac6a in do_source /home/guest/trung/vim3/src/scriptfile.c:1801
#18 0x55b4aa6b77a3 in cmd_source /home/guest/trung/vim3/src/scriptfile.c:1174
#19 0x55b4aa6b7804 in ex_source /home/guest/trung/vim3/src/scriptfile.c:1200
#20 0x55b4aa3a17c9 in do_one_cmd /home/guest/trung/vim3/src/ex_docmd.c:2570
#21 0x55b4aa398b4f in do_cmdline /home/guest/trung/vim3/src/ex_docmd.c:992
#22 0x55b4aa396f4e in do_cmdline_cmd /home/guest/trung/vim3/src/ex_docmd.c:586
#23 0x55b4aa987cc6 in exe_commands /home/guest/trung/vim3/src/main.c:3133
#24 0x55b4aa980ebb in vim_main2 /home/guest/trung/vim3/src/main.c:780
#25 0x55b4aa980777 in main /home/guest/trung/vim3/src/main.c:432
#26 0x7f58a05c9c86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21c86)
SUMMARY: AddressSanitizer: heap-buffer-overflow (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x79779)
Shadow bytes around the buggy address:
0x0c047fff8f90: fa fa fd fa fa fa fd fa fa fa fd fd fa fa fd fa
0x0c047fff8fa0: fa fa fd fa fa fa fd fa fa fa fd fd fa fa fd fa
0x0c047fff8fb0: fa fa fd fa fa fa fd fa fa fa 02 fa fa fa 00 fa
0x0c047fff8fc0: fa fa 02 fa fa fa fd fa fa fa fd fd fa fa fd fa
0x0c047fff8fd0: fa fa 02 fa fa fa fd fa fa fa fd fa fa fa 05 fa
=>0x0c047fff8fe0: fa fa[07]fa fa fa 00 04 fa fa 01 fa fa fa 01 fa
0x0c047fff8ff0: fa fa 01 fa fa fa 01 fa fa fa 07 fa fa fa 03 fa
0x0c047fff9000: fa fa 00 06 fa fa 00 04 fa fa 01 fa fa fa 01 fa
0x0c047fff9010: fa fa 03 fa fa fa 01 fa fa fa 01 fa fa fa 01 fa
0x0c047fff9020: fa fa 01 fa fa fa 01 fa fa fa 01 fa fa fa 01 fa
0x0c047fff9030: fa fa 02 fa fa fa fd fa fa fa fd fa fa fa fd fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==26557==ABORTING
Attachment
Impact
Typically, this can result in corruption of data, a crash, or code execution.
Occurrences
We are processing your report and will contact the
vim
team within 24 hours.
a year ago
We have contacted a member of the
vim
team and are waiting to hear back
a year ago
We have sent a
follow up to the
vim
team.
We will try again in 7 days.
a year ago
Well, this turned out to be tricky to reproduce, but I could see the mistake in the code from the stack trace.
The researcher's credibility has increased: +7
ex_docmd.c#L3123
has been validated
to join this conversation