issue_owner_repo
listlengths
2
2
issue_body
stringlengths
0
261k
issue_title
stringlengths
1
925
issue_comments_url
stringlengths
56
81
issue_comments_count
int64
0
2.5k
issue_created_at
stringlengths
20
20
issue_updated_at
stringlengths
20
20
issue_html_url
stringlengths
37
62
issue_github_id
int64
387k
2.46B
issue_number
int64
1
127k
[ "WebAssembly", "wabt" ]
here is my test code ``` (module (func (result i32) (i32.add (i32.const 624485) (i32.const 2)))) ``` LEB of 624485 [should be 0xE58E26](https://en.wikipedia.org/wiki/LEB128#Unsigned_LEB128) But from the prototype if get ``` ; function 0 .... 0000014: 0a ; OPCODE_I32_CONST 0000015: 6587 0900 ; u32 literal .... ``` how is 0x65870900 derived?
LEB128 question
https://api.github.com/repos/WebAssembly/wabt/issues/8/comments
4
2015-11-20T19:13:34Z
2015-11-20T21:45:05Z
https://github.com/WebAssembly/wabt/issues/8
118,107,165
8
[ "WebAssembly", "wabt" ]
I have a test that generated the following code, and fed it into sexpr-wasm (module (func $foomore(call $foo (i32.const 0x0)) ) (func $foo (param i32)(nop)) ) Note the lack of space between $foomore and its opening paren. Sometime between rev 64fb062d and rev 7601228b this stopped being accepted by the parser, which now issues the following confusing error: <filename>:2:23: expected '(', not "$foo" It looks like the "(call" is getting sucked into the "$foomore" token. I don't actually know what the rules of s-expressions are in that case; maybe this is the correct behavior?
Whitespace between function name token and left paren
https://api.github.com/repos/WebAssembly/wabt/issues/6/comments
2
2015-10-13T19:28:18Z
2015-10-14T00:28:29Z
https://github.com/WebAssembly/wabt/issues/6
111,252,358
6
[ "WebAssembly", "wabt" ]
The spec interpreter reports assertion errors with line numbers from the source. This would be really handy for debugging codegen issues (e.g. in a test suite with hundreds of assertions, which one is failing?). Currently WAOT just tracks and prints the count (i.e. "assertion number X failed") but a line number would be even better. That would have more immediate utility but at some point it might become nice to have line information for expressions too (maybe I want to generate debug info?) That's sort of a speculative use case and may not matter during the time horizon that sexpr-wasm matters, but something that might be nice to have in mind. I'd be happy for asserts for now. I don't know if it would be better just to hang SourceLocations off of some existing data structure, or pass extra callback args or what, it doesn't matter much to me, I don't think.
Provide a way to get SourceLocations
https://api.github.com/repos/WebAssembly/wabt/issues/4/comments
4
2015-10-10T22:46:12Z
2015-10-19T07:30:00Z
https://github.com/WebAssembly/wabt/issues/4
110,821,326
4
[ "yasm", "yasm" ]
I have the following snippet in my code, with the idea of creating a compilation error if an impossible set of defines are set: ``` %if LABEL && ALTLABEL %error cant have LABEL and ALTLABEL together %endif ``` In nasm this behaves as expected. In yasm I get the message, but then yasm returns with exit code 0, with the broken code as output. I can workaround it by specifying "-Werror": "Treat warnings as errors". But it already is an error. I think the error is here: https://github.com/yasm/yasm/blob/121ab150b3577b666c79a79f4a511798d7ad2432/modules/preprocs/nasm/nasm-pp.c#L2875 should be ERR_FATAL instead of ERR_NONFATAL
%error macro only leads to a warning/different behaviour than nasm
https://api.github.com/repos/yasm/yasm/issues/278/comments
0
2024-06-27T12:15:32Z
2024-06-27T12:15:32Z
https://github.com/yasm/yasm/issues/278
2,377,998,112
278
[ "yasm", "yasm" ]
Hi, developers. I have detected an access violation at `nasm-pp.c:4765:21` in the latest commit version 9defefa. ### System I discover this crash with a docker container configured with 1 CPU core of Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz and the 64-bit Ubuntu 18.04 LTS. ### Version `9defefa` ### Program `yasm` ### Build ```sh export ASAN_OPTIONS=detect_leaks=0 ./autogen.sh ./configure make -j $(nproc) ``` ### Run ```sh ./yasm ./yasm-poc5 ``` ### PoC One PoC file in this zip. [yasm-poc5.zip](https://github.com/user-attachments/files/15806102/yasm-poc5.zip) ### Crash ``` yasm: file name already has no extension: output will be in `yasm.out' AddressSanitizer:DEADLYSIGNAL ================================================================= ==7081==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000001 (pc 0x000000580d70 bp 0x7ffe10f783c0 sp 0x7ffe10f77e80 T0) ==7081==The signal is caused by a READ memory access. ==7081==Hint: address points to the zero page. #0 0x580d70 in expand_mmacro /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:4765:21 #1 0x5689fd in pp_getline /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5129:18 #2 0x56151b in nasm_preproc_get_line /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-preproc.c:203:12 #3 0x551395 in nasm_parser_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parse.c:219:13 #4 0x550fdf in nasm_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:66:5 #5 0x550985 in nasm_parser_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:83:5 #6 0x4ca7d6 in do_assemble /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:641:5 #7 0x4c832e in main /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:877:12 #8 0x7c73942f1c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41b9c9 in _start (/out/yasm+0x41b9c9) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:4765:21 in expand_mmacro ==7081==ABORTING ```
null-pointer-dereference at nasm-pp.c:4765:21 (9defefa)
https://api.github.com/repos/yasm/yasm/issues/277/comments
0
2024-06-12T13:52:01Z
2024-06-12T13:52:01Z
https://github.com/yasm/yasm/issues/277
2,348,837,907
277
[ "yasm", "yasm" ]
Hi, developers. I have detected a heap-buffer-overflow crash at `nasm-pp.c:3902:34` in the latest commit version 9defefa. ### System I discover this crash with a docker container configured with 1 CPU core of Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz and the 64-bit Ubuntu 18.04 LTS. ### Version `9defefa` ### Program `yasm` ### Build ```sh export ASAN_OPTIONS=detect_leaks=0 ./autogen.sh ./configure make -j $(nproc) ``` ### Run ```sh ./yasm ./yasm-poc4 ``` ### PoC One PoC file in this zip. [yasm-poc4.zip](https://github.com/user-attachments/files/15752807/yasm-poc4.zip) ### Crash ``` yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==13539==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x603000004bc8 at pc 0x00000056c2bd bp 0x7ffda2b49690 sp 0x7ffda2b49688 READ of size 8 at 0x603000004bc8 thread T0 #0 0x56c2bc in expand_mmac_params /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:3902:34 #1 0x5685cf in pp_getline /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5079:21 #2 0x56151b in nasm_preproc_get_line /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-preproc.c:203:12 #3 0x551395 in nasm_parser_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parse.c:219:13 #4 0x550fdf in nasm_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:66:5 #5 0x550985 in nasm_parser_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:83:5 #6 0x4ca7d6 in do_assemble /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:641:5 #7 0x4c832e in main /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:877:12 #8 0x7b7a7a5dfc86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41b9c9 in _start (/out/yasm+0x41b9c9) 0x603000004bc8 is located 8 bytes to the left of 24-byte region [0x603000004bd0,0x603000004be8) allocated by thread T0 here: #0 0x496ba9 in realloc (/out/yasm+0x496ba9) #1 0x5157bc in def_xrealloc /src/targets/yasm_latest/repo/libyasm/xmalloc.c:101:18 #2 0x590e12 in is_mmacro /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:4591:25 #3 0x57f856 in expand_mmacro /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:4660:9 #4 0x5689fd in pp_getline /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5129:18 #5 0x56151b in nasm_preproc_get_line /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-preproc.c:203:12 #6 0x551395 in nasm_parser_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parse.c:219:13 #7 0x550fdf in nasm_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:66:5 #8 0x550985 in nasm_parser_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:83:5 #9 0x4ca7d6 in do_assemble /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:641:5 #10 0x4c832e in main /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:877:12 #11 0x7b7a7a5dfc86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-buffer-overflow /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:3902:34 in expand_mmac_params Shadow bytes around the buggy address: 0x0c067fff8920: fd fd fd fa fa fa 00 00 00 fa fa fa fd fd fd fd 0x0c067fff8930: fa fa 00 00 00 fa fa fa 00 00 02 fa fa fa fd fd 0x0c067fff8940: fd fa fa fa 00 00 00 fa fa fa 00 00 00 fa fa fa 0x0c067fff8950: 00 00 00 fa fa fa 00 00 00 fa fa fa 00 00 00 fa 0x0c067fff8960: fa fa 00 00 00 fa fa fa 00 00 00 fa fa fa 00 00 =>0x0c067fff8970: 00 fa fa fa 00 00 00 fa fa[fa]00 00 00 fa fa fa 0x0c067fff8980: 00 00 00 fa fa fa 00 00 00 fa fa fa 00 00 00 fa 0x0c067fff8990: fa fa 00 00 00 fa fa fa 00 00 00 fa fa fa fd fd 0x0c067fff89a0: fd fa fa fa fd fd fd fa fa fa fd fd fd fa fa fa 0x0c067fff89b0: fd fd fd fa fa fa 00 00 00 00 fa fa fd fd fd fa 0x0c067fff89c0: fa fa fd fd fd fa fa fa fa fa fa fa fa fa fa 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 Shadow gap: cc ==13539==ABORTING ```
heap-buffer-overflow at nasm-pp.c:3902:34 (9defefa)
https://api.github.com/repos/yasm/yasm/issues/276/comments
0
2024-06-09T14:09:52Z
2024-06-09T14:09:52Z
https://github.com/yasm/yasm/issues/276
2,342,277,934
276
[ "yasm", "yasm" ]
Hi, developers. I have detected a heap-use-after-free crash at nasm-pp.c:5025:39 in the latest commit version 9defefa. ### System I discover this crash with a docker container configured with 1 CPU core of Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz and the 64-bit Ubuntu 18.04 LTS. ### Version `9defefa` ### Program `yasm` ### Build ```sh export ASAN_OPTIONS=detect_leaks=0 ./autogen.sh ./configure make -j $(nproc) ``` ### Run ```sh ./yasm ./yasm-poc3 ``` ### PoC One PoC file in this zip. [yasm-poc3.zip](https://github.com/user-attachments/files/15752722/yasm-poc3.zip) ### Crash ``` yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==13537==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e000001338 at pc 0x000000567e0f bp 0x7ffed63b8aa0 sp 0x7ffed63b8a98 READ of size 4 at 0x60e000001338 thread T0 #0 0x567e0e in pp_getline /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5025:39 #1 0x56151b in nasm_preproc_get_line /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-preproc.c:203:12 #2 0x551395 in nasm_parser_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parse.c:219:13 #3 0x550fdf in nasm_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:66:5 #4 0x550985 in nasm_parser_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:83:5 #5 0x4ca7d6 in do_assemble /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:641:5 #6 0x4c832e in main /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:877:12 #7 0x73e8a7220c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #8 0x41b9c9 in _start (/out/yasm+0x41b9c9) 0x60e000001338 is located 152 bytes inside of 160-byte region [0x60e0000012a0,0x60e000001340) freed by thread T0 here: #0 0x496622 in free (/out/yasm+0x496622) #1 0x515814 in def_xfree /src/targets/yasm_latest/repo/libyasm/xmalloc.c:113:5 #2 0x56a089 in free_mmacro /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:1163:5 #3 0x567bc7 in pp_getline /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5010:25 #4 0x56151b in nasm_preproc_get_line /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-preproc.c:203:12 #5 0x551395 in nasm_parser_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parse.c:219:13 #6 0x550fdf in nasm_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:66:5 #7 0x550985 in nasm_parser_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:83:5 #8 0x4ca7d6 in do_assemble /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:641:5 #9 0x4c832e in main /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:877:12 #10 0x73e8a7220c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 previously allocated by thread T0 here: #0 0x49688d in malloc (/out/yasm+0x49688d) #1 0x5156c7 in def_xmalloc /src/targets/yasm_latest/repo/libyasm/xmalloc.c:69:14 #2 0x57649d in do_directive /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:3212:24 #3 0x5685dc in pp_getline /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5084:13 #4 0x56151b in nasm_preproc_get_line /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-preproc.c:203:12 #5 0x551395 in nasm_parser_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parse.c:219:13 #6 0x550fdf in nasm_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:66:5 #7 0x550985 in nasm_parser_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:83:5 #8 0x4ca7d6 in do_assemble /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:641:5 #9 0x4c832e in main /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:877:12 #10 0x73e8a7220c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-use-after-free /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5025:39 in pp_getline Shadow bytes around the buggy address: 0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8230: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00 0x0c1c7fff8240: 00 00 00 00 00 00 00 00 00 00 00 00 fa fa fa fa 0x0c1c7fff8250: fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd =>0x0c1c7fff8260: fd fd fd fd fd fd fd[fd]fa fa fa fa fa fa fa fa 0x0c1c7fff8270: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c1c7fff8280: fd fd fd fd fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff8290: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff82a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c1c7fff82b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 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 Shadow gap: cc ==13537==ABORTING ```
heap-use-after-free at nasm-pp.c:5025:39 (9defefa)
https://api.github.com/repos/yasm/yasm/issues/275/comments
0
2024-06-09T13:53:49Z
2024-06-09T13:53:49Z
https://github.com/yasm/yasm/issues/275
2,342,271,158
275
[ "yasm", "yasm" ]
Hi, developers. I have detected a heap-use-after-free crash at nasm-pp.c:3879:33 in the latest commit version 9defefa. ### System I discover this crash with a docker container configured with 1 CPU core of Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz and the 64-bit Ubuntu 18.04 LTS. ### Version `9defefa` ### Program `yasm` ### Build ```sh export ASAN_OPTIONS=detect_leaks=0 ./autogen.sh ./configure make -j $(nproc) ``` ### Run ```sh ./yasm ./yasm-poc2 ``` ### PoC One PoC file in this zip. [yasm-poc2.zip](https://github.com/user-attachments/files/15752664/yasm-poc2.zip) ### Crash ``` yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==13529==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000011c8 at pc 0x00000056bf4d bp 0x7ffcef213f70 sp 0x7ffcef213f68 READ of size 8 at 0x60e0000011c8 thread T0 #0 0x56bf4c in expand_mmac_params /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:3879:33 #1 0x5685cf in pp_getline /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5079:21 #2 0x56151b in nasm_preproc_get_line /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-preproc.c:203:12 #3 0x551395 in nasm_parser_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parse.c:219:13 #4 0x550fdf in nasm_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:66:5 #5 0x550985 in nasm_parser_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:83:5 #6 0x4ca7d6 in do_assemble /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:641:5 #7 0x4c832e in main /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:877:12 #8 0x7c0942370c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41b9c9 in _start (/out/yasm+0x41b9c9) 0x60e0000011c8 is located 8 bytes inside of 160-byte region [0x60e0000011c0,0x60e000001260) freed by thread T0 here: #0 0x496622 in free (/out/yasm+0x496622) #1 0x515814 in def_xfree /src/targets/yasm_latest/repo/libyasm/xmalloc.c:113:5 #2 0x56a089 in free_mmacro /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:1163:5 #3 0x567bc7 in pp_getline /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5010:25 #4 0x56151b in nasm_preproc_get_line /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-preproc.c:203:12 #5 0x551395 in nasm_parser_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parse.c:219:13 #6 0x550fdf in nasm_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:66:5 #7 0x550985 in nasm_parser_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:83:5 #8 0x4ca7d6 in do_assemble /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:641:5 #9 0x4c832e in main /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:877:12 #10 0x7c0942370c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 previously allocated by thread T0 here: #0 0x49688d in malloc (/out/yasm+0x49688d) #1 0x5156c7 in def_xmalloc /src/targets/yasm_latest/repo/libyasm/xmalloc.c:69:14 #2 0x57649d in do_directive /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:3212:24 #3 0x5685dc in pp_getline /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5084:13 #4 0x56151b in nasm_preproc_get_line /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-preproc.c:203:12 #5 0x551395 in nasm_parser_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parse.c:219:13 #6 0x550fdf in nasm_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:66:5 #7 0x550985 in nasm_parser_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:83:5 #8 0x4ca7d6 in do_assemble /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:641:5 #9 0x4c832e in main /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:877:12 #10 0x7c0942370c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-use-after-free /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:3879:33 in expand_mmac_params Shadow bytes around the buggy address: 0x0c1c7fff81e0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff81f0: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 0x0c1c7fff8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c1c7fff8230: fa fa fa fa fa fa fa fa fd[fd]fd fd fd fd fd fd 0x0c1c7fff8240: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa 0x0c1c7fff8250: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8260: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 0x0c1c7fff8270: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c1c7fff8280: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 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 Shadow gap: cc ==13529==ABORTING ```
heap-use-after-free at nasm-pp.c:3879:33 (9defefa)
https://api.github.com/repos/yasm/yasm/issues/274/comments
0
2024-06-09T13:33:28Z
2024-06-09T13:33:28Z
https://github.com/yasm/yasm/issues/274
2,342,254,357
274
[ "yasm", "yasm" ]
Hi, developers. I have detected an access violation at nasm-pp.c:3816:17 in the latest commit version 9defefa. ### System I discover this crash with a docker container configured with 1 CPU core of Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz and the 64-bit Ubuntu 18.04 LTS. ### Version `9defefa` ### Program `yasm` ### Build ```sh export ASAN_OPTIONS=detect_leaks=0 ./autogen.sh ./configure make -j $(nproc) ``` ### Run ```sh ./yasm ./yasm-poc1 ``` ### PoC One PoC file in this zip. [yasm-poc1.zip](https://github.com/user-attachments/files/15752604/yasm-poc1.zip) ### Crash ``` yasm: file name already has no extension: output will be in `yasm.out' AddressSanitizer:DEADLYSIGNAL ================================================================= ==13525==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000018 (pc 0x0000005882fa bp 0x7ffdb1488ff0 sp 0x7ffdb1488f50 T0) ==13525==The signal is caused by a READ memory access. ==13525==Hint: address points to the zero page. #0 0x5882fa in find_cc /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:3816:17 #1 0x56ceb6 in expand_mmac_params /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:3987:34 #2 0x5685cf in pp_getline /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:5079:21 #3 0x56151b in nasm_preproc_get_line /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-preproc.c:203:12 #4 0x551395 in nasm_parser_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parse.c:219:13 #5 0x550fdf in nasm_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:66:5 #6 0x550985 in nasm_parser_do_parse /src/targets/yasm_latest/repo/modules/parsers/nasm/nasm-parser.c:83:5 #7 0x4ca7d6 in do_assemble /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:641:5 #8 0x4c832e in main /src/targets/yasm_latest/repo/frontends/yasm/yasm.c:877:12 #9 0x7b4669fd2c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #10 0x41b9c9 in _start (/out/yasm+0x41b9c9) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /src/targets/yasm_latest/repo/modules/preprocs/nasm/nasm-pp.c:3816:17 in find_cc ==13525==ABORTING ```
null-pointer-dereference at nasm-pp.c:3816:17 (9defefa)
https://api.github.com/repos/yasm/yasm/issues/273/comments
0
2024-06-09T13:03:28Z
2024-06-12T13:52:42Z
https://github.com/yasm/yasm/issues/273
2,342,239,708
273
[ "yasm", "yasm" ]
When running the test suite of 9defefa on Fedora rawhide (gcc-14.0.1, binutils-2.42.50), I'm getting the following test failure on x86 32-bit (i686) arch: ``` $ cat test-suite.log ================================== yasm 1.3.0: ./test-suite.log ================================== # TOTAL: 44 # PASS: 43 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: modules/objfmts/macho/tests/nasm64/macho64_test.sh ======================================================== Test macho_test: .O.. +3-1/4 75% ** O: macho64-buildversion did not match object file! FAIL modules/objfmts/macho/tests/nasm64/macho64_test.sh (exit status: 1) ```
macho64_test failure on x86 32-bit
https://api.github.com/repos/yasm/yasm/issues/270/comments
0
2024-03-22T10:37:20Z
2024-03-22T10:37:20Z
https://github.com/yasm/yasm/issues/270
2,202,199,029
270
[ "yasm", "yasm" ]
When building latest git HEAD (9defefa), the test suite (`make check`) fails randomly if run in parallel with `make -jN`.
test suite fails randomly with parallel make
https://api.github.com/repos/yasm/yasm/issues/269/comments
0
2024-03-22T09:52:09Z
2024-03-22T09:52:09Z
https://github.com/yasm/yasm/issues/269
2,202,113,166
269
[ "yasm", "yasm" ]
Hello, I am a graduate student specializing in static analysis of programs. Recently, while using a static analysis tool to detect issues in open-source projects, I found several defects in the project. The description of the defects can be found at the following link:https://github.com/LuMingYinDetect/yasm_defects/blob/main/yasm_detect_2.md
The vulnerability is a memory leak bug located at line 71 of the file /yasm/tools/genmacro/genmacro.c
https://api.github.com/repos/yasm/yasm/issues/268/comments
0
2024-02-28T07:39:04Z
2024-02-28T07:39:04Z
https://github.com/yasm/yasm/issues/268
2,158,309,795
268
[ "yasm", "yasm" ]
Hello, I am a graduate student specializing in static analysis of programs. Recently, while using a static analysis tool to detect issues in open-source projects, I found several defects in the project. The description of the defects can be found at the following link:https://github.com/LuMingYinDetect/yasm_defects/blob/main/yasm_detect_1.md
The defect occurs at line 177 in the file /yasm/modules/preprocs/nasm/nasmlib.c
https://api.github.com/repos/yasm/yasm/issues/267/comments
0
2024-02-28T07:38:26Z
2024-02-28T07:38:26Z
https://github.com/yasm/yasm/issues/267
2,158,308,867
267
[ "yasm", "yasm" ]
#### Description: ~~~shell AddressSanitizer: heap-use-after-free /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:1116:20 in expr_traverse_nodes_post ~~~ #### Project: <https://github.com/yasm/yasm> #### Version: ~~~bash fk@localhost:/mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master$ ./yasm --version yasm 1.3.0 Copyright (c) 2001-2014 Peter Johnson and other Yasm developers. Run yasm --license for licensing overview and summary. ~~~ #### Env: ~~~bash Ubuntu 22.04.3 LTS Ubuntu clang version 14.0.0-1ubuntu1.1 gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ~~~ #### Reproduce: ~~~shell ./autogen.sh export CC=afl-clang-fast CXX=afl-clang-fast++ AFL_USE_ASAN=1 ASAN_OPTIONS=detect_leaks=0 ./configure make ./yasm poc.in ~~~ #### ASAN: ~~~bash fk@localhost:/mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/crashes$ ./yasm id_000000,sig_06,src_005623,time_11506018,execs_3448900,op_havoc,rep_1 yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==27760==ERROR: AddressSanitizer: heap-use-after-free on address 0x6060000005d0 at pc 0x562d0f641065 bp 0x7ffd4c6ac830 sp 0x7ffd4c6ac828 READ of size 4 at 0x6060000005d0 thread T0 #0 0x562d0f641064 in expr_traverse_nodes_post /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:1116:20 #1 0x562d0f645809 in yasm_expr_destroy /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:1049:5 #2 0x562d0f645809 in expr_delete_term /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:1028:17 #3 0x562d0f645809 in expr_simplify_identity /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:582:17 #4 0x562d0f63d501 in expr_level_op /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:702:17 #5 0x562d0f63fe04 in expr_level_tree /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:881:9 #6 0x562d0f63ee6f in yasm_expr__level_tree /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:907:9 #7 0x562d0f568569 in yasm_value_finalize /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/value.c:546:18 #8 0x562d0f636edd in bc_data_finalize /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/bc-data.c:117:21 #9 0x562d0f63a9a4 in yasm_bc_finalize /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/bytecode.c:176:9 #10 0x562d0f5594bd in yasm_object_finalize /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/section.c:546:13 #11 0x562d0f508b2a in do_assemble /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/frontends/yasm/yasm.c:647:5 #12 0x7f0dd706bd8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 #13 0x7f0dd706be3f in __libc_start_main csu/../csu/libc-start.c:392:3 #14 0x562d0f4454b4 in _start (/mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/crashes/yasm+0xba4b4) (BuildId: 4ca98d63b28f16b0ca05fb7a63c14ceb11a123a9) 0x6060000005d0 is located 16 bytes inside of 56-byte region [0x6060000005c0,0x6060000005f8) freed by thread T0 here: #0 0x562d0f4cac32 in free (/mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/crashes/yasm+0x13fc32) (BuildId: 4ca98d63b28f16b0ca05fb7a63c14ceb11a123a9) #1 0x562d0f64103a in expr_destroy_each /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:1041:5 #2 0x562d0f64103a in expr_traverse_nodes_post /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:1123:12 previously allocated by thread T0 here: #0 0x562d0f4caede in __interceptor_malloc (/mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/crashes/yasm+0x13fede) (BuildId: 4ca98d63b28f16b0ca05fb7a63c14ceb11a123a9) #1 0x562d0f56c153 in def_xmalloc /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/xmalloc.c:69:14 SUMMARY: AddressSanitizer: heap-use-after-free /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:1116:20 in expr_traverse_nodes_post Shadow bytes around the buggy address: 0x0c0c7fff8060: fa fa fa fa fd fd fd fd fd fd fd fa fa fa fa fa 0x0c0c7fff8070: fd fd fd fd fd fd fd fa fa fa fa fa fd fd fd fd 0x0c0c7fff8080: fd fd fd fa fa fa fa fa fd fd fd fd fd fd fd fa 0x0c0c7fff8090: fa fa fa fa fd fd fd fd fd fd fd fa fa fa fa fa 0x0c0c7fff80a0: fd fd fd fd fd fd fd fa fa fa fa fa fd fd fd fd =>0x0c0c7fff80b0: fd fd fd fa fa fa fa fa fd fd[fd]fd fd fd fd fa 0x0c0c7fff80c0: fa fa fa fa fd fd fd fd fd fd fd fa fa fa fa fa 0x0c0c7fff80d0: fd fd fd fd fd fd fd fa fa fa fa fa fd fd fd fd 0x0c0c7fff80e0: fd fd fd fa fa fa fa fa fd fd fd fd fd fd fd fa 0x0c0c7fff80f0: fa fa fa fa 00 00 00 00 00 00 00 fa fa fa fa fa 0x0c0c7fff8100: 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 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 ==27760==ABORTING ~~~ #### POC: <https://github.com/OraclePi/fuzzing/blob/main/yasm/expr_traverse_nodes_post/input/id_000000%2Csig_06%2Csrc_005623%2Ctime_11506018%2Cexecs_3448900%2Cop_havoc%2Crep_1>
heap-use-after-free in /libyasm/expr.c:1116:20 in expr_traverse_nodes_post
https://api.github.com/repos/yasm/yasm/issues/262/comments
0
2024-01-25T12:49:49Z
2024-01-25T12:57:12Z
https://github.com/yasm/yasm/issues/262
2,100,327,671
262
[ "yasm", "yasm" ]
#### Description: ~~~shell AddressSanitizer: SEGV /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/modules/preprocs/nasm/nasm-pp.c:3862:20 in expand_mmac_params ==27727==ABORTING ~~~ #### Project: <https://github.com/yasm/yasm> #### Version: ~~~bash fk@localhost:/mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master$ ./yasm --version yasm 1.3.0 Copyright (c) 2001-2014 Peter Johnson and other Yasm developers. Run yasm --license for licensing overview and summary. ~~~ #### Env: ~~~bash Ubuntu 22.04.3 LTS Ubuntu clang version 14.0.0-1ubuntu1.1 gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ~~~ #### Reproduce: ~~~shell ./autogen.sh export CC=afl-clang-fast CXX=afl-clang-fast++ AFL_USE_ASAN=1 ASAN_OPTIONS=detect_leaks=0 ./configure make ./yasm poc.in ~~~ #### ASAN: ~~~bash fk@localhost:/mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master$ ./yasm id\:000000\,sig\:11\,src\:004450\,time\:17949411\,execs\:1756333\,op\:havoc\,rep\:14 yasm: file name already has no extension: output will be in `yasm.out' AddressSanitizer:DEADLYSIGNAL ================================================================= ==27727==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000001 (pc 0x55b6497d1f50 bp 0x7ffca37d6e70 sp 0x7ffca37d6d60 T0) ==27727==The signal is caused by a READ memory access. ==27727==Hint: address points to the zero page. #0 0x55b6497d1f50 in expand_mmac_params /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/modules/preprocs/nasm/nasm-pp.c:3862:20 #1 0x55b6497c9417 in pp_getline /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/modules/preprocs/nasm/nasm-pp.c:5079:21 #2 0x55b6497c2880 in nasm_preproc_get_line /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/modules/preprocs/nasm/nasm-preproc.c:203:12 #3 0x55b6497b83a6 in nasm_parser_parse /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/modules/parsers/nasm/nasm-parse.c:219:13 #4 0x55b6497b6032 in nasm_do_parse /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/modules/parsers/nasm/nasm-parser.c:66:5 #5 0x55b6497b6032 in nasm_parser_do_parse /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/modules/parsers/nasm/nasm-parser.c:83:5 #6 0x55b649722b09 in do_assemble /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/frontends/yasm/yasm.c:641:5 #7 0x7f3afadc3d8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16 #8 0x7f3afadc3e3f in __libc_start_main csu/../csu/libc-start.c:392:3 #9 0x55b64965f4b4 in _start (/mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/yasm+0xba4b4) (BuildId: 4ca98d63b28f16b0ca05fb7a63c14ceb11a123a9) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/modules/preprocs/nasm/nasm-pp.c:3862:20 in expand_mmac_params ==27727==ABORTING ~~~ #### POC: <https://github.com/OraclePi/fuzzing/blob/main/yasm/expand_mmac_params/input/id%EF%80%BA000000%2Csig%EF%80%BA11%2Csrc%EF%80%BA004450%2Ctime%EF%80%BA17949411%2Cexecs%EF%80%BA1756333%2Cop%EF%80%BAhavoc%2Crep%EF%80%BA14>
SEGV in /modules/preprocs/nasm/nasm-pp.c:3862:20 in expand_mmac_params
https://api.github.com/repos/yasm/yasm/issues/261/comments
0
2024-01-25T12:31:25Z
2024-01-25T12:55:28Z
https://github.com/yasm/yasm/issues/261
2,100,296,161
261
[ "yasm", "yasm" ]
I might be asking this in the wrong place, but after creating an installer using this tool, how do I get the newly created installer to run silently without any user interaction?
Which flag allows for silent installation?
https://api.github.com/repos/yasm/yasm/issues/260/comments
0
2024-01-24T00:41:38Z
2024-01-24T00:41:38Z
https://github.com/yasm/yasm/issues/260
2,097,210,152
260
[ "yasm", "yasm" ]
My compile script: ``` git clone https://github.com/yasm/yasm.git cd yasm ./autogen.sh ./configure \ --host=x86_64-w64-mingw32 \ --target=x86_64-w64-mingw32 \ --prefix=target make make install ``` error as below: ``` I am going to run ./configure with --enable-maintainer-mode If you wish to pass any other args to it, please specify them on the ./autogen.sh command line. Generating configuration files for yasm, please wait.... aclocal -I m4 1.3.0.86.g9def autoheader automake -a configure.ac:72: installing 'config/compile' configure.ac:14: installing 'config/install-sh' configure.ac:14: installing 'config/missing' Makefile.am: installing 'config/depcomp' parallel-tests: installing 'config/test-driver' autoconf configure.ac:12: warning: The macro 'AC_CONFIG_HEADER' is obsolete. configure.ac:12: You should run autoupdate. ./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from... configure.ac:12: the top level configure.ac:21: warning: The macro 'AC_HELP_STRING' is obsolete. configure.ac:21: You should run autoupdate. ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from... configure.ac:21: the top level configure.ac:30: warning: The macro 'AC_HELP_STRING' is obsolete. configure.ac:30: You should run autoupdate. ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from... configure.ac:30: the top level configure.ac:38: warning: The macro 'AC_HELP_STRING' is obsolete. configure.ac:38: You should run autoupdate. ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from... configure.ac:38: the top level configure.ac:46: warning: The macro 'AC_HELP_STRING' is obsolete. configure.ac:46: You should run autoupdate. ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from... configure.ac:46: the top level configure.ac:54: warning: The macro 'AC_HELP_STRING' is obsolete. configure.ac:54: You should run autoupdate. ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from... configure.ac:54: the top level configure.ac:62: warning: The macro 'AC_HELP_STRING' is obsolete. configure.ac:62: You should run autoupdate. ./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from... configure.ac:62: the top level configure.ac:73: warning: The macro 'AC_PROG_CC_STDC' is obsolete. configure.ac:73: You should run autoupdate. ./lib/autoconf/c.m4:1669: AC_PROG_CC_STDC is expanded from... configure.ac:73: the top level configure.ac:113: warning: The macro 'AC_TRY_COMPILE' is obsolete. configure.ac:113: You should run autoupdate. ./lib/autoconf/general.m4:2845: AC_TRY_COMPILE is expanded from... lib/m4sugar/m4sh.m4:690: _AS_IF_ELSE is expanded from... lib/m4sugar/m4sh.m4:697: AS_IF is expanded from... ./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from... m4/ax_create_stdint_h.m4:119: AX_CREATE_STDINT_H is expanded from... configure.ac:113: the top level configure.ac:280: warning: The macro 'AC_FD_CC' is obsolete. configure.ac:280: You should run autoupdate. ./lib/autoconf/general.m4:399: AC_FD_CC is expanded from... lib/m4sugar/m4sh.m4:690: _AS_IF_ELSE is expanded from... lib/m4sugar/m4sh.m4:697: AS_IF is expanded from... ./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from... m4/cython.m4:6: CYTHON_CHECK_VERSION is expanded from... configure.ac:280: the top level configure.ac:285: warning: The macro 'AC_TRY_CPP' is obsolete. configure.ac:285: You should run autoupdate. ./lib/autoconf/general.m4:2762: AC_TRY_CPP is expanded from... m4/pythonhead.m4:5: AM_CHECK_PYTHON_HEADERS is expanded from... configure.ac:285: the top level configure --enable-maintainer-mode checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a race-free mkdir -p... /usr/sbin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking whether make supports the include directive... yes (GNU style) checking for gcc... /__w/toolchain/toolchain/cross/bin/x86_64-w64-mingw32-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.exe checking for suffix of executables... .exe configure: error: in '/__w/toolchain/toolchain/source/yasm': configure: error: cannot run C compiled programs. If you meant to cross compile, use '--host'. See 'config.log' for more details checking whether we are cross compiling... Error: Process completed with exit code 1. ``` And the configure and config.log: [configure.zip](https://github.com/yasm/yasm/files/13984067/configure.zip) [config.log](https://github.com/yasm/yasm/files/13984068/config.log)
configure error when cross-compile on linux
https://api.github.com/repos/yasm/yasm/issues/258/comments
0
2024-01-19T04:05:11Z
2024-01-19T04:05:11Z
https://github.com/yasm/yasm/issues/258
2,089,531,385
258
[ "yasm", "yasm" ]
### 1.version: yasm v1.3.0 ### 2.test environment ubuntu 18.04 TLS ### 3.build yasm with asan $ export CC=/usr/bin/clang $ export CXX=/usr/bin/clang++ $ ./configure --disable-shared CFLAGS="-fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -ggdb" $ make ### 4 run it ../yasm -w poc ### 5.ASAN report crashes_type: yasm: file name already has no extension: output will be in `yasm.out' crashes/id:000146,sig:11,src:002083,op:ext_AO,pos:44:1: error: junk at end of line, first unrecognized character is `/' crashes/id:000146,sig:11,src:002083,op:ext_AO,pos:44:2: error: undefined symbol `rep' in preprocessor crashes/id:000146,sig:11,src:002083,op:ext_AO,pos:44:2: error: undefined symbol `struc' in preprocessor crashes/id:000146,sig:11,src:002083,op:ext_AO,pos:44:2: warning: trailing garbage after expression ignored crashes/id:000146,sig:11,src:002083,op:ext_AO,pos:44:2: error: non-constant value given to `%rep' crashes/id:000146,sig:11,src:002083,op:ext_AO,pos:44:3: error: `%endm': not defining a macro ================================================================= ==118137==ERROR: LeakSanitizer: detected memory leaks Direct leak of 45 byte(s) in 13 object(s) allocated from: #0 0x7fd4a61ffb40 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb40) #1 0x564e5f9e7fd4 in def_xmalloc libyasm/xmalloc.c:69 #2 0x564e5fa299f5 in new_Token modules/preprocs/nasm/nasm-pp.c:1512 #3 0x564e5fa293fb in tokenise modules/preprocs/nasm/nasm-pp.c:1425 #4 0x564e5fa42c86 in pp_getline modules/preprocs/nasm/nasm-pp.c:5030 #5 0x564e5fa20be0 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:195 #6 0x564e5fa155c3 in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:218 #7 0x564e5fa140af in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #8 0x564e5fa14230 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #9 0x564e5f9ad901 in do_assemble frontends/yasm/yasm.c:519 #10 0x564e5f9ae6bf in main frontends/yasm/yasm.c:749 #11 0x7fd4a5d51c86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21c86) Direct leak of 4 byte(s) in 1 object(s) allocated from: #0 0x7fd4a61ffb40 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb40) #1 0x564e5f9e7fd4 in def_xmalloc libyasm/xmalloc.c:69 #2 0x564e5fa299f5 in new_Token modules/preprocs/nasm/nasm-pp.c:1512 #3 0x564e5fa3c832 in expand_smacro modules/preprocs/nasm/nasm-pp.c:4104 #4 0x564e5fa35a41 in do_directive modules/preprocs/nasm/nasm-pp.c:3174 #5 0x564e5fa430aa in pp_getline modules/preprocs/nasm/nasm-pp.c:5075 #6 0x564e5fa20be0 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:195 #7 0x564e5fa155c3 in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:218 #8 0x564e5fa140af in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #9 0x564e5fa14230 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #10 0x564e5f9ad901 in do_assemble frontends/yasm/yasm.c:519 #11 0x564e5f9ae6bf in main frontends/yasm/yasm.c:749 #12 0x7fd4a5d51c86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21c86) SUMMARY: AddressSanitizer: 49 byte(s) leaked in 14 allocation(s). ### poc https://github.com/hanxuer/crashes/blob/main/yasm/04/poc ### source code nasm-pp.c else { if (txtlen == 0) txtlen = strlen(text); t->text = nasm_malloc(1 + txtlen); <-- this strncpy(t->text, text, txtlen); t->text[txtlen] = '\0'; }
Memory leak vulnerability discovered
https://api.github.com/repos/yasm/yasm/issues/257/comments
2
2023-12-28T02:06:30Z
2024-01-19T15:26:39Z
https://github.com/yasm/yasm/issues/257
2,057,907,048
257
[ "yasm", "yasm" ]
# project https://github.com/yasm/yasm Commit: 9defefa # os info Ubuntu18.04 TLS # poc [poc.zip](https://github.com/yasm/yasm/files/13631095/poc.zip) # build ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure && make ./yasm poc # ASAN Info 14582==ERROR: AddressSanitizer: heap-use-after-free on address 0x607000000c00 at pc 0x00000061e0a0 bp 0x7ffc6b109460 sp 0x7ffc6b109458 READ of size 4 at 0x607000000c00 thread T0 #0 0x61e09f in expr_traverse_nodes_post /benchmark/yasm/libyasm/expr.c:1116:20 #1 0x61e012 in yasm_expr_destroy /benchmark/yasm/libyasm/expr.c:1049:5 #2 0x62304e in expr_delete_term /benchmark/yasm/libyasm/expr.c:1028:17 #3 0x6228b8 in expr_simplify_identity /benchmark/yasm/libyasm/expr.c:582:17 #4 0x61ad18 in expr_level_op /benchmark/yasm/libyasm/expr.c:702:17 #5 0x61d4b1 in expr_level_tree /benchmark/yasm/libyasm/expr.c:881:9 #6 0x61c762 in yasm_expr__level_tree /benchmark/yasm/libyasm/expr.c:907:9 #7 0x61f409 in yasm_expr_get_intnum /benchmark/yasm/libyasm/expr.c:1265:11 #8 0x503522 in recalc_normal_span /benchmark/yasm/libyasm/section.c:1044:15 #9 0x4fe928 in yasm_object_optimize /benchmark/yasm/libyasm/section.c:1392:20 #10 0x4c9700 in do_assemble /benchmark/yasm/frontends/yasm/yasm.c:651:5 #11 0x4c71fe in main /benchmark/yasm/frontends/yasm/yasm.c:877:12 #12 0x7f4b09dca082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 #13 0x41c3cd in _start (/benchmark/yasm/yasm+0x41c3cd) 0x607000000c00 is located 16 bytes inside of 72-byte region [0x607000000bf0,0x607000000c38) freed by thread T0 here: #0 0x4972a2 in free /src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:127:3 #1 0x5146e4 in def_xfree /benchmark/yasm/libyasm/xmalloc.c:113:5 #2 0x61e27c in expr_destroy_each /benchmark/yasm/libyasm/expr.c:1041:5 #3 0x61e18d in expr_traverse_nodes_post /benchmark/yasm/libyasm/expr.c:1123:12 #4 0x61e012 in yasm_expr_destroy /benchmark/yasm/libyasm/expr.c:1049:5 #5 0x62304e in expr_delete_term /benchmark/yasm/libyasm/expr.c:1028:17 #6 0x6228b8 in expr_simplify_identity /benchmark/yasm/libyasm/expr.c:582:17 #7 0x61ad18 in expr_level_op /benchmark/yasm/libyasm/expr.c:702:17 #8 0x61d4b1 in expr_level_tree /benchmark/yasm/libyasm/expr.c:881:9 #9 0x61c762 in yasm_expr__level_tree /benchmark/yasm/libyasm/expr.c:907:9 #10 0x61f409 in yasm_expr_get_intnum /benchmark/yasm/libyasm/expr.c:1265:11 #11 0x503522 in recalc_normal_span /benchmark/yasm/libyasm/section.c:1044:15 #12 0x4fe928 in yasm_object_optimize /benchmark/yasm/libyasm/section.c:1392:20 #13 0x4c9700 in do_assemble /benchmark/yasm/frontends/yasm/yasm.c:651:5 #14 0x4c71fe in main /benchmark/yasm/frontends/yasm/yasm.c:877:12 #15 0x7f4b09dca082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 previously allocated by thread T0 here: #0 0x49750d in malloc /src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:145:3 #1 0x514597 in def_xmalloc /benchmark/yasm/libyasm/xmalloc.c:69:14 #2 0x61d89f in yasm_expr__copy_except /benchmark/yasm/libyasm/expr.c:1002:9 #3 0x61dd46 in expr_item_copy /benchmark/yasm/libyasm/expr.c:973:31 #4 0x61db0a in yasm_expr__copy_except /benchmark/yasm/libyasm/expr.c:1010:13 #5 0x50325e in recalc_normal_span /benchmark/yasm/libyasm/section.c:1035:31 #6 0x4fe928 in yasm_object_optimize /benchmark/yasm/libyasm/section.c:1392:20 #7 0x4c9700 in do_assemble /benchmark/yasm/frontends/yasm/yasm.c:651:5 #8 0x4c71fe in main /benchmark/yasm/frontends/yasm/yasm.c:877:12 #9 0x7f4b09dca082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 SUMMARY: AddressSanitizer: heap-use-after-free /benchmark/yasm/libyasm/expr.c:1116:20 in expr_traverse_nodes_post Shadow bytes around the buggy address: 0x0c0e7fff8130: 00 00 00 fa fa fa fa fa 00 00 00 00 00 00 00 00 0x0c0e7fff8140: 00 fa fa fa fa fa 00 00 00 00 00 00 00 00 00 fa 0x0c0e7fff8150: fa fa fa fa 00 00 00 00 00 00 00 00 00 fa fa fa 0x0c0e7fff8160: fa fa fd fd fd fd fd fd fd fd fd fa fa fa fa fa 0x0c0e7fff8170: fd fd fd fd fd fd fd fd fd fa fa fa fa fa fd fd =>0x0c0e7fff8180:[fd]fd fd fd fd fd fd fa fa fa fa fa fa fa fa fa 0x0c0e7fff8190: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0e7fff81a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0e7fff81b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0e7fff81c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0e7fff81d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 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 Shadow gap: cc
heap-use-after-free yasm/libyasm/expr.c:1116 in expr_traverse_nodes_post
https://api.github.com/repos/yasm/yasm/issues/256/comments
0
2023-12-11T04:53:37Z
2024-01-11T10:53:28Z
https://github.com/yasm/yasm/issues/256
2,034,827,460
256
[ "yasm", "yasm" ]
This seems to appear every time I pass `-Werror` to yasm. It not only seems redundant, but it also makes it harder to visually identify any actual errors. What's the intention of this message? Is it possible to suppress it? `nasm` doesn't seem to print this.
`error: warnings being treated as errors`
https://api.github.com/repos/yasm/yasm/issues/255/comments
3
2023-12-07T20:08:57Z
2023-12-07T20:35:57Z
https://github.com/yasm/yasm/issues/255
2,031,444,525
255
[ "yasm", "yasm" ]
In nasm `mov a, [foo wrt ..got]` (or `..gotpc`?) creates a GOTPCREL relocation, but yasm specifies this as `mov a, [foo wrt ..gotpcrel]`. Is the syntax difference intentional?
x86-64 GOTPCREL wrt syntax doesn't match nasm
https://api.github.com/repos/yasm/yasm/issues/254/comments
1
2023-11-30T21:57:02Z
2023-11-30T22:28:23Z
https://github.com/yasm/yasm/issues/254
2,019,576,075
254
[ "yasm", "yasm" ]
**The name of an affected Product** [yasm](https://github.com/yasm/yasm) **The affected version** Commit: [9defefa](https://github.com/yasm/yasm/commit/9defefae9fbcb6958cddbfa778c1ea8605da8b8b) yasm 1.3.0.86.g9def **Description** An issue in yasm 1.3.0.86.g9def allows a attacker to cause a denial of service via the yasm_section_bcs_first function in the libyasm/section.c component. **Vulnerability Type** segmentation violation **Environment** - Operating System ```` Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic ```` - Compiler ```` Ubuntu clang version 12.0.1-++20211102090516+fed41342a82f-1~exp1~20211102211019.11 Target: x86_64-pc-linux-gnu Thread model: posix ```` **Steps to Reproduce** download [poc.zip](https://github.com/yasm/yasm/files/13466305/poc.zip), then ```` git clone https://github.com/yasm/yasm cd yasm git checkout 9defefa ./autogen.sh make distclean CC=clang \ CXX=clang++ \ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" \ CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" \ ./configure make -j $(nproc) unzip poc.zip # run command ./yasm poc ```` **ASAN Info** ```` yasm: file name already has no extension: output will be in `yasm.out' AddressSanitizer:DEADLYSIGNAL ================================================================= ==4485==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000040 (pc 0x0000004fe6c6 bp 0x7ffdc1e64920 sp 0x7ffdc1e64910 T0) ==4485==The signal is caused by a READ memory access. ==4485==Hint: address points to the zero page. #0 0x4fe6c6 in yasm_section_bcs_first /yasm/libyasm/section.c:619:12 #1 0x55ad2f in parse_expr6 /yasm/modules/parsers/nasm/nasm-parse.c:1486:21 #2 0x55bbfd in parse_expr5 /yasm/modules/parsers/nasm/nasm-parse.c:1306:9 #3 0x55b8ad in parse_expr4 /yasm/modules/parsers/nasm/nasm-parse.c:1278:9 #4 0x55b54d in parse_expr3 /yasm/modules/parsers/nasm/nasm-parse.c:1250:9 #5 0x55b36a in parse_expr2 /yasm/modules/parsers/nasm/nasm-parse.c:1243:5 #6 0x55b18a in parse_expr1 /yasm/modules/parsers/nasm/nasm-parse.c:1237:5 #7 0x55904a in parse_expr0 /yasm/modules/parsers/nasm/nasm-parse.c:1231:5 #8 0x558e6a in parse_bexpr /yasm/modules/parsers/nasm/nasm-parse.c:1225:5 #9 0x55f2af in parse_operand /yasm/modules/parsers/nasm/nasm-parse.c:1043:28 #10 0x554545 in parse_instr /yasm/modules/parsers/nasm/nasm-parse.c:751:41 #11 0x55511f in parse_exp /yasm/modules/parsers/nasm/nasm-parse.c:566:10 #12 0x551e07 in parse_line /yasm/modules/parsers/nasm/nasm-parse.c:289:10 #13 0x5516e8 in nasm_parser_parse /yasm/modules/parsers/nasm/nasm-parse.c:231:18 #14 0x550fdf in nasm_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:66:5 #15 0x550985 in nasm_parser_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:83:5 #16 0x4ca7d6 in do_assemble /yasm/frontends/yasm/yasm.c:641:5 #17 0x4c832e in main /yasm/frontends/yasm/yasm.c:877:12 #18 0x7f2094cb4c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #19 0x41b9c9 in _start (/yasm/yasm+0x41b9c9) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /yasm/libyasm/section.c:619:12 in yasm_section_bcs_first ==4485==ABORTING ```` **Source Code** ````c 616 yasm_bytecode * 617 yasm_section_bcs_first(yasm_section *sect) 618 { --->619 return STAILQ_FIRST(&sect->bcs); 620 } 621 622 yasm_bytecode * 623 yasm_section_bcs_last(yasm_section *sect) 624 { ````
SEGV in yasm_section_bcs_first() at libyasm/section.c:619
https://api.github.com/repos/yasm/yasm/issues/253/comments
1
2023-11-26T08:48:59Z
2024-01-03T11:22:18Z
https://github.com/yasm/yasm/issues/253
2,010,956,429
253
[ "yasm", "yasm" ]
**The name of an affected Product** [yasm](https://github.com/yasm/yasm) **The affected version** Commit: [9defefa](https://github.com/yasm/yasm/commit/9defefae9fbcb6958cddbfa778c1ea8605da8b8b) yasm 1.3.0.86.g9def **Description** An issue in yasm 1.3.0.86.g9def allows a attacker to cause a denial of service via the expand_mmac_params function in the modules/preprocs/nasm/nasm-pp.c component. **Vulnerability Type** segmentation violation **Environment** - Operating System ```` Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic ```` - Compiler ```` Ubuntu clang version 12.0.1-++20211102090516+fed41342a82f-1~exp1~20211102211019.11 Target: x86_64-pc-linux-gnu Thread model: posix ```` **Steps to Reproduce** download [poc.zip](https://github.com/yasm/yasm/files/13465912/poc.zip), then ```` git clone https://github.com/yasm/yasm cd yasm git checkout 9defefa ./autogen.sh make distclean CC=clang \ CXX=clang++ \ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" \ CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" \ ./configure make -j $(nproc) unzip poc.zip # run command ./yasm poc ```` **ASAN Info** ```` yasm: file name already has no extension: output will be in `yasm.out' AddressSanitizer:DEADLYSIGNAL ================================================================= ==4490==ERROR: AddressSanitizer: SEGV on unknown address 0x60ffffffffc8 (pc 0x00000056d207 bp 0x7ffd39055dc0 sp 0x7ffd39055740 T0) ==4490==The signal is caused by a READ memory access. #0 0x56d207 in expand_mmac_params /yasm/modules/preprocs/nasm/nasm-pp.c:4013:47 #1 0x5685cf in pp_getline /yasm/modules/preprocs/nasm/nasm-pp.c:5079:21 #2 0x56151b in nasm_preproc_get_line /yasm/modules/preprocs/nasm/nasm-preproc.c:203:12 #3 0x551395 in nasm_parser_parse /yasm/modules/parsers/nasm/nasm-parse.c:219:13 #4 0x550fdf in nasm_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:66:5 #5 0x550985 in nasm_parser_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:83:5 #6 0x4ca7d6 in do_assemble /yasm/frontends/yasm/yasm.c:641:5 #7 0x4c832e in main /yasm/frontends/yasm/yasm.c:877:12 #8 0x7f79d306fc86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41b9c9 in _start (/yasm/yasm+0x41b9c9) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /yasm/modules/preprocs/nasm/nasm-pp.c:4013:47 in expand_mmac_params ==4490==ABORTING ```` **Source Code** ```` 4009 tt = mac->params[n]; 4010 } 4011 if (tt) 4012 { --->4013 for (i = 0; i < mac->paramlen[n]; i++) 4014 { 4015 *tail = 4016 new_Token(NULL, tt->type, tt->text, 4017 0); 4018 tail = &(*tail)->next; ````
SEGV in the function expand_mmac_params() at modules/preprocs/nasm/nasm-pp.c:4013
https://api.github.com/repos/yasm/yasm/issues/252/comments
3
2023-11-26T04:38:16Z
2024-03-23T09:32:24Z
https://github.com/yasm/yasm/issues/252
2,010,889,074
252
[ "yasm", "yasm" ]
I enabled "generate debug information: Yes (-g cv8)", breakpoints do not work in asm file. ![image](https://github.com/yasm/yasm/assets/31180871/21d7563f-cafb-4527-9216-b8084b62286b) Used this to install yasm in VS2017: https://github.com/ShiftMediaProject/VSYASM asm file: ``` section .text global _my_asmz _my_asmz: push ebp ; save base pointer mov ebp, esp ; set up new base pointer mov eax, [ebp+8] ; get first argument add eax, 1 ; add 1 to it mov esp, ebp ; restore stack pointer pop ebp ; restore base pointer ret ; return the value in eax ``` main.cpp: ``` #include <iostream> extern "C" int my_asmz(int); //using namespace std; int main() { int x = 43; int y = my_asmz(x); std::cout << "x = " << x << ", y = " << y << std::endl; std::system("pause"); return 0; } ```
Does yasm integrated in VS2017 support breakpoint in mixed cpp and asm file?
https://api.github.com/repos/yasm/yasm/issues/251/comments
0
2023-11-24T12:15:58Z
2023-11-24T12:15:58Z
https://github.com/yasm/yasm/issues/251
2,009,632,297
251
[ "yasm", "yasm" ]
**The name of an affected Product** [yasm](https://github.com/yasm/yasm) **The affected version** Commit: [9defefa](https://github.com/yasm/yasm/commit/9defefae9fbcb6958cddbfa778c1ea8605da8b8b) yasm 1.3.0.86.g9def **Description** An issue in yasm 1.3.0.86.g9def allows a attacker to cause a denial of service via the expr_delete_term function in the libyasm/expr.c component. **Vulnerability Type** Buffer Overflow **Environment** - Operating System ```` Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic ```` - Compiler ```` Ubuntu clang version 12.0.1-++20211102090516+fed41342a82f-1~exp1~20211102211019.11 Target: x86_64-pc-linux-gnu Thread model: posix ```` **Steps to Reproduce** download [poc.zip](https://github.com/yasm/yasm/files/13415866/poc.zip), then ```` git clone https://github.com/yasm/yasm cd yasm git checkout 9defefa ./autogen.sh make distclean CC=clang \ CXX=clang++ \ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" \ CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" \ ./configure make -j $(nproc) unzip poc.zip # run command ./yasm poc ```` **ASAN info** ```` yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==4526==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x606000022498 at pc 0x00000062409c bp 0x7ffe67167c80 sp 0x7ffe67167c78 READ of size 4 at 0x606000022498 thread T0 #0 0x62409b in expr_delete_term /yasm/libyasm/expr.c:1019:19 #1 0x6239e8 in expr_simplify_identity /yasm/libyasm/expr.c:582:17 #2 0x61cdde in expr_level_op /yasm/libyasm/expr.c:792:23 #3 0x61e5e1 in expr_level_tree /yasm/libyasm/expr.c:881:9 #4 0x61e290 in expr_level_tree /yasm/libyasm/expr.c:865:17 #5 0x61e290 in expr_level_tree /yasm/libyasm/expr.c:865:17 #6 0x61d892 in yasm_expr__level_tree /yasm/libyasm/expr.c:907:9 #7 0x620539 in yasm_expr_get_intnum /yasm/libyasm/expr.c:1265:11 #8 0x612914 in yasm_bc_create_data /yasm/libyasm/bc-data.c:357:24 #9 0x5561cb in parse_exp /yasm/modules/parsers/nasm/nasm-parse.c:669:20 #10 0x551e07 in parse_line /yasm/modules/parsers/nasm/nasm-parse.c:289:10 #11 0x5516e8 in nasm_parser_parse /yasm/modules/parsers/nasm/nasm-parse.c:231:18 #12 0x550fdf in nasm_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:66:5 #13 0x550985 in nasm_parser_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:83:5 #14 0x4ca7d6 in do_assemble /yasm/frontends/yasm/yasm.c:641:5 #15 0x4c832e in main /yasm/frontends/yasm/yasm.c:877:12 #16 0x7f5599036c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #17 0x41b9c9 in _start (/yasm/yasm+0x41b9c9) 0x606000022498 is located 0 bytes to the right of 56-byte region [0x606000022460,0x606000022498) allocated by thread T0 here: #0 0x496ba9 in realloc (/yasm/yasm+0x496ba9) #1 0x5157bc in def_xrealloc /yasm/libyasm/xmalloc.c:101:18 #2 0x61c515 in expr_level_op /yasm/libyasm/expr.c:738:9 #3 0x61e5e1 in expr_level_tree /yasm/libyasm/expr.c:881:9 #4 0x61e290 in expr_level_tree /yasm/libyasm/expr.c:865:17 #5 0x61e290 in expr_level_tree /yasm/libyasm/expr.c:865:17 #6 0x61d892 in yasm_expr__level_tree /yasm/libyasm/expr.c:907:9 #7 0x620539 in yasm_expr_get_intnum /yasm/libyasm/expr.c:1265:11 #8 0x612914 in yasm_bc_create_data /yasm/libyasm/bc-data.c:357:24 #9 0x5561cb in parse_exp /yasm/modules/parsers/nasm/nasm-parse.c:669:20 #10 0x551e07 in parse_line /yasm/modules/parsers/nasm/nasm-parse.c:289:10 #11 0x5516e8 in nasm_parser_parse /yasm/modules/parsers/nasm/nasm-parse.c:231:18 #12 0x550fdf in nasm_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:66:5 #13 0x550985 in nasm_parser_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:83:5 #14 0x4ca7d6 in do_assemble /yasm/frontends/yasm/yasm.c:641:5 #15 0x4c832e in main /yasm/frontends/yasm/yasm.c:877:12 #16 0x7f5599036c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-buffer-overflow /yasm/libyasm/expr.c:1019:19 in expr_delete_term Shadow bytes around the buggy address: 0x0c0c7fffc440: fa fa fa fa fd fd fd fd fd fd fd fa fa fa fa fa 0x0c0c7fffc450: fd fd fd fd fd fd fd fa fa fa fa fa fd fd fd fd 0x0c0c7fffc460: fd fd fd fa fa fa fa fa fd fd fd fd fd fd fd fa 0x0c0c7fffc470: fa fa fa fa fd fd fd fd fd fd fd fa fa fa fa fa 0x0c0c7fffc480: fd fd fd fd fd fd fd fa fa fa fa fa 00 00 00 00 =>0x0c0c7fffc490: 00 00 00[fa]fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fffc4a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fffc4b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fffc4c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fffc4d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fffc4e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 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 Shadow gap: cc ==4526==ABORTING ````
heap-buffer-overflow in the function expr_delete_term() at libyasm/expr.c:1019
https://api.github.com/repos/yasm/yasm/issues/250/comments
1
2023-11-20T14:26:40Z
2024-02-12T16:51:53Z
https://github.com/yasm/yasm/issues/250
2,002,324,400
250
[ "yasm", "yasm" ]
**The name of an affected Product** [yasm](https://github.com/yasm/yasm) **The affected version** Commit: [9defefa](https://github.com/yasm/yasm/commit/9defefae9fbcb6958cddbfa778c1ea8605da8b8b) yasm 1.3.0.86.g9def **Description** An issue in yasm 1.3.0.86.g9def allows a attacker to cause a denial of service via the do_directive function in the modules/preprocs/nasm/nasm-pp.c component. **Vulnerability Type** Use After Free **Environment** - Operating System ```` Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic ```` - Compiler ```` Ubuntu clang version 12.0.1-++20211102090516+fed41342a82f-1~exp1~20211102211019.11 Target: x86_64-pc-linux-gnu Thread model: posix ```` **Steps to Reproduce** download [poc.zip](https://github.com/yasm/yasm/files/13415757/poc.zip), then ```` git clone https://github.com/yasm/yasm cd yasm git checkout 9defefa ./autogen.sh make distclean CC=clang \ CXX=clang++ \ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" \ CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" \ ./configure make -j $(nproc) unzip poc.zip # run command ./yasm poc ```` **ASAN info** ```` yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==4513==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000011f0 at pc 0x00000056e946 bp 0x7fff5a439c10 sp 0x7fff5a439c08 READ of size 4 at 0x60e0000011f0 thread T0 #0 0x56e945 in do_directive /yasm/modules/preprocs/nasm/nasm-pp.c:2389:38 #1 0x5685dc in pp_getline /yasm/modules/preprocs/nasm/nasm-pp.c:5084:13 #2 0x56151b in nasm_preproc_get_line /yasm/modules/preprocs/nasm/nasm-preproc.c:203:12 #3 0x551395 in nasm_parser_parse /yasm/modules/parsers/nasm/nasm-parse.c:219:13 #4 0x550fdf in nasm_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:66:5 #5 0x550985 in nasm_parser_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:83:5 #6 0x4ca7d6 in do_assemble /yasm/frontends/yasm/yasm.c:641:5 #7 0x4c832e in main /yasm/frontends/yasm/yasm.c:877:12 #8 0x7f7cd4d0dc86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41b9c9 in _start (/yasm/yasm+0x41b9c9) 0x60e0000011f0 is located 48 bytes inside of 160-byte region [0x60e0000011c0,0x60e000001260) freed by thread T0 here: #0 0x496622 in free (/yasm/yasm+0x496622) #1 0x515814 in def_xfree /yasm/libyasm/xmalloc.c:113:5 #2 0x56a089 in free_mmacro /yasm/modules/preprocs/nasm/nasm-pp.c:1163:5 #3 0x567bc7 in pp_getline /yasm/modules/preprocs/nasm/nasm-pp.c:5010:25 #4 0x56151b in nasm_preproc_get_line /yasm/modules/preprocs/nasm/nasm-preproc.c:203:12 #5 0x551395 in nasm_parser_parse /yasm/modules/parsers/nasm/nasm-parse.c:219:13 #6 0x550fdf in nasm_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:66:5 #7 0x550985 in nasm_parser_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:83:5 #8 0x4ca7d6 in do_assemble /yasm/frontends/yasm/yasm.c:641:5 #9 0x4c832e in main /yasm/frontends/yasm/yasm.c:877:12 #10 0x7f7cd4d0dc86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 previously allocated by thread T0 here: #0 0x49688d in malloc (/yasm/yasm+0x49688d) #1 0x5156c7 in def_xmalloc /yasm/libyasm/xmalloc.c:69:14 #2 0x57649d in do_directive /yasm/modules/preprocs/nasm/nasm-pp.c:3212:24 #3 0x5685dc in pp_getline /yasm/modules/preprocs/nasm/nasm-pp.c:5084:13 #4 0x56151b in nasm_preproc_get_line /yasm/modules/preprocs/nasm/nasm-preproc.c:203:12 #5 0x551395 in nasm_parser_parse /yasm/modules/parsers/nasm/nasm-parse.c:219:13 #6 0x550fdf in nasm_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:66:5 #7 0x550985 in nasm_parser_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:83:5 #8 0x4ca7d6 in do_assemble /yasm/frontends/yasm/yasm.c:641:5 #9 0x4c832e in main /yasm/frontends/yasm/yasm.c:877:12 #10 0x7f7cd4d0dc86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: heap-use-after-free /yasm/modules/preprocs/nasm/nasm-pp.c:2389:38 in do_directive Shadow bytes around the buggy address: 0x0c1c7fff81e0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff81f0: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 0x0c1c7fff8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c1c7fff8230: fa fa fa fa fa fa fa fa fd fd fd fd fd fd[fd]fd 0x0c1c7fff8240: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa 0x0c1c7fff8250: fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd 0x0c1c7fff8260: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa 0x0c1c7fff8270: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8280: 00 00 00 00 fa fa fa fa fa fa fa fa fa fa fa 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 Shadow gap: cc ==4513==ABORTING ````
heap-use-after-free in the function do_directive() at modules/preprocs/nasm/nasm-pp.c:2389
https://api.github.com/repos/yasm/yasm/issues/249/comments
0
2023-11-20T14:16:57Z
2024-01-03T11:22:46Z
https://github.com/yasm/yasm/issues/249
2,002,305,193
249
[ "yasm", "yasm" ]
**The name of an affected Product** [yasm](https://github.com/yasm/yasm) **The affected version** Commit: [9defefa](https://github.com/yasm/yasm/commit/9defefae9fbcb6958cddbfa778c1ea8605da8b8b) yasm 1.3.0.86.g9def **Description** An issue in yasm 1.3.0.86.g9def allows a attacker to cause a denial of service via the expand_smacro function in the modules/preprocs/nasm/nasm-pp.c component. **Vulnerability Type** segmentation violation **Environment** - Operating System ```` Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic ```` - Compiler ```` Ubuntu clang version 12.0.1-++20211102090516+fed41342a82f-1~exp1~20211102211019.11 Target: x86_64-pc-linux-gnu Thread model: posix ```` **Steps to Reproduce** download [poc.zip](https://github.com/yasm/yasm/files/13415602/poc.zip), then ```` git clone https://github.com/yasm/yasm cd yasm git checkout 9defefa ./autogen.sh make distclean CC=clang \ CXX=clang++ \ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" \ CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" \ ./configure make -j $(nproc) unzip poc.zip # run command ./yasm poc ```` **ASAN info** ```` yasm: file name already has no extension: output will be in `yasm.out' AddressSanitizer:DEADLYSIGNAL ================================================================= ==4495==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000018 (pc 0x00000057e43b bp 0x7ffd326b7640 sp 0x7ffd326b6e40 T0) ==4495==The signal is caused by a READ memory access. ==4495==Hint: address points to the zero page. #0 0x57e43b in expand_smacro /yasm/modules/preprocs/nasm/nasm-pp.c:4357:63 #1 0x5689f0 in pp_getline /yasm/modules/preprocs/nasm/nasm-pp.c:5128:21 #2 0x56151b in nasm_preproc_get_line /yasm/modules/preprocs/nasm/nasm-preproc.c:203:12 #3 0x551395 in nasm_parser_parse /yasm/modules/parsers/nasm/nasm-parse.c:219:13 #4 0x550fdf in nasm_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:66:5 #5 0x550985 in nasm_parser_do_parse /yasm/modules/parsers/nasm/nasm-parser.c:83:5 #6 0x4ca7d6 in do_assemble /yasm/frontends/yasm/yasm.c:641:5 #7 0x4c832e in main /yasm/frontends/yasm/yasm.c:877:12 #8 0x7f229c330c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #9 0x41b9c9 in _start (/yasm/yasm+0x41b9c9) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /yasm/modules/preprocs/nasm/nasm-pp.c:4357:63 in expand_smacro ==4495==ABORTING ````
SEGV in the function expand_smacro() at modules/preprocs/nasm/nasm-pp.c:4357
https://api.github.com/repos/yasm/yasm/issues/248/comments
2
2023-11-20T14:03:30Z
2024-01-04T10:06:59Z
https://github.com/yasm/yasm/issues/248
2,002,278,782
248
[ "yasm", "yasm" ]
Hi, we found a null pointer dereference bug in the latest version of yasm. ### ASAN ``` ==55571==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000048 (pc 0x000000577e9b bp 0x7fffe279e490 sp 0x7fffe279e290 T0) ==55571==The signal is caused by a READ memory access. ==55571==Hint: address points to the zero page. #0 0x577e9b in yasm_section_bcs_append /root/yasm/libyasm/section.c:634:13 #1 0x5c3aa0 in nasm_parser_parse /root/yasm/modules/parsers/nasm/nasm-parse.c:264:23 #2 0x5c15fa in nasm_do_parse /root/yasm/modules/parsers/nasm/nasm-parser.c:66:5 #3 0x5c15fa in nasm_parser_do_parse /root/yasm/modules/parsers/nasm/nasm-parser.c:83:5 #4 0x4f3239 in do_assemble /root/yasm/frontends/yasm/yasm.c:641:5 #5 0x4f3239 in main /root/yasm/frontends/yasm/yasm.c:877:12 #6 0x7f48dfb49c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 #7 0x41ba39 in _start (/root/yasm/yasm+0x41ba39) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /root/yasm/libyasm/section.c:634:13 in yasm_section_bcs_append ==55571==ABORTING ``` ### Version ``` # git log commit 9defefae9fbcb6958cddbfa778c1ea8605da8b8b (HEAD -> master, origin/master, origin/HEAD) Author: dataisland <[email protected]> Date: Fri Sep 22 00:21:20 2023 -0500 Fix null-pointer-dereference in yasm_expr_get_intnum (#244) ``` ### How to reproduce Build yasm with ASAN, then run ``` ./yasm $POC ``` The POC can be found here. [POC](https://github.com/TimChan2001/pocs/raw/main/poc-yasm-2) We ran it on a 64-bit Ubuntu 18.04.
NULL Pointer Dereference in yasm_section_bcs_append at section.c:634
https://api.github.com/repos/yasm/yasm/issues/247/comments
0
2023-10-28T15:11:35Z
2023-10-28T15:11:35Z
https://github.com/yasm/yasm/issues/247
1,966,632,045
247
[ "yasm", "yasm" ]
Hi, we found memory leaks in the latest version of yasm. ### ASAN ``` ==42150==ERROR: LeakSanitizer: detected memory leaks Direct leak of 56 byte(s) in 1 object(s) allocated from: #0 0x4ac0a0 in malloc /root/build/llvm_tools/llvm-11.0.0.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:145 #1 0x58d3b8 in def_xmalloc /root/yasm/libyasm/xmalloc.c:69:14 #2 0x5c205e in parse_line /root/yasm/modules/parsers/nasm/nasm-parse.c:289:10 #3 0x5c205e in nasm_parser_parse /root/yasm/modules/parsers/nasm/nasm-parse.c:231:18 #4 0x5c15fa in nasm_do_parse /root/yasm/modules/parsers/nasm/nasm-parser.c:66:5 #5 0x5c15fa in nasm_parser_do_parse /root/yasm/modules/parsers/nasm/nasm-parser.c:83:5 #6 0x4f3239 in do_assemble /root/yasm/frontends/yasm/yasm.c:641:5 #7 0x4f3239 in main /root/yasm/frontends/yasm/yasm.c:877:12 #8 0x7f7c36042c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 Indirect leak of 128 byte(s) in 1 object(s) allocated from: #0 0x4ac0a0 in malloc /root/build/llvm_tools/llvm-11.0.0.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:145 #1 0x58d3b8 in def_xmalloc /root/yasm/libyasm/xmalloc.c:69:14 #2 0x5c51fb in parse_exp /root/yasm/modules/parsers/nasm/nasm-parse.c:578:13 #3 0x5c205e in parse_line /root/yasm/modules/parsers/nasm/nasm-parse.c:289:10 #4 0x5c205e in nasm_parser_parse /root/yasm/modules/parsers/nasm/nasm-parse.c:231:18 #5 0x5c15fa in nasm_do_parse /root/yasm/modules/parsers/nasm/nasm-parser.c:66:5 #6 0x5c15fa in nasm_parser_do_parse /root/yasm/modules/parsers/nasm/nasm-parser.c:83:5 #7 0x4f3239 in do_assemble /root/yasm/frontends/yasm/yasm.c:641:5 #8 0x4f3239 in main /root/yasm/frontends/yasm/yasm.c:877:12 #9 0x7f7c36042c86 in __libc_start_main /build/glibc-CVJwZb/glibc-2.27/csu/../csu/libc-start.c:310 SUMMARY: AddressSanitizer: 184 byte(s) leaked in 2 allocation(s). ``` ### Version ``` # git log commit 9defefae9fbcb6958cddbfa778c1ea8605da8b8b (HEAD -> master, origin/master, origin/HEAD) Author: dataisland <[email protected]> Date: Fri Sep 22 00:21:20 2023 -0500 Fix null-pointer-dereference in yasm_expr_get_intnum (#244) ``` ### How to reproduce Build yasm with ASAN, then run ``` ./yasm $POC ``` The POC can be found here. [POC](https://github.com/TimChan2001/pocs/raw/main/poc-yasm-1) We ran it on a 64-bit Ubuntu 18.04.
Memory leaks found.
https://api.github.com/repos/yasm/yasm/issues/246/comments
0
2023-10-27T15:54:57Z
2023-10-27T15:54:57Z
https://github.com/yasm/yasm/issues/246
1,965,795,866
246
[ "yasm", "yasm" ]
hi! * i am looking for some alternate to the Turbo Assembled (tasm) * for doing the practical for the subject of MicroProcessors 8086 (so, i want to see the value of registers, flags, segments etc) * using VSCodium or some dedicated IDE. I found yasm via [alternativeto][yasm-alt2] & i have read the [yasm-site] but i can't find which one to use. [yasm-site]: http://yasm.tortall.net [yasm-alt2]: https://alternativeto.net/browse/search/?q=nasm#item-3949c529-0955-e211-9c6a-0025902c7e73
differences from nasm and which one to use?
https://api.github.com/repos/yasm/yasm/issues/245/comments
1
2023-10-26T13:38:23Z
2024-02-03T21:27:48Z
https://github.com/yasm/yasm/issues/245
1,963,603,855
245
[ "yasm", "yasm" ]
The 1.3.0 release provides [yasm-1.3.0-win64.exe](http://www.tortall.net/projects/yasm/releases/yasm-1.3.0-win64.exe), which needs `MSVCRT100.dll`. However, this dll is not installed by default on the Windows-2022 Github runners. So it would be useful to, when a next release is done, to provide binaries that don't need any system C library.
Provide MSVC runtime-free binary releases
https://api.github.com/repos/yasm/yasm/issues/240/comments
0
2023-09-04T21:57:38Z
2023-09-04T21:57:38Z
https://github.com/yasm/yasm/issues/240
1,880,901,969
240
[ "yasm", "yasm" ]
Hello Yasm developers, We recently conducted a fuzzing test on yasm and discovered an UAF bug. We would like to provide a detailed description of the bug and seek your assistance in addressing it. version: Yasm: 1.3.0 gcc:gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ubuntu: 20.04 command to reproduce: yasm [UAF](https://github.com/shinibufa/crash_seeds/blob/main/yasm/UAF) ASAN report: ================================================================= ==2673798==ERROR: AddressSanitizer: heap-use-after-free on address 0x602000006ed0 at pc 0x55772d5a2ec3 bp 0x7ffc63666bf0 sp 0x7ffc63666be0 READ of size 8 at 0x602000006ed0 thread T0 #0 0x55772d5a2ec2 in yasm_floatnum_destroy libyasm/floatnum.c:509 #1 0x55772d6892a1 in expr_delete_term libyasm/expr.c:1020 #2 0x55772d6861a8 in expr_simplify_identity libyasm/expr.c:582 #3 0x55772d68711f in expr_level_op libyasm/expr.c:701 #4 0x55772d6887df in expr_level_tree libyasm/expr.c:880 #5 0x55772d688849 in expr_level_tree libyasm/expr.c:886 #6 0x55772d68859d in expr_level_tree libyasm/expr.c:864 #7 0x55772d6889a3 in yasm_expr__level_tree libyasm/expr.c:906 #8 0x55772d647a0e in bin_objfmt_output_value modules/objfmts/bin/bin-objfmt.c:954 #9 0x55772d67c8b6 in bc_data_tobytes libyasm/bc-data.c:226 #10 0x55772d682c9b in yasm_bc_tobytes libyasm/bytecode.c:341 #11 0x55772d647c94 in bin_objfmt_output_bytecode modules/objfmts/bin/bin-objfmt.c:984 #12 0x55772d5ac83a in yasm_section_bcs_traverse libyasm/section.c:637 #13 0x55772d6486ac in bin_objfmt_output_section modules/objfmts/bin/bin-objfmt.c:1082 #14 0x55772d5ac1ad in yasm_object_sections_traverse libyasm/section.c:544 #15 0x55772d64a709 in bin_objfmt_output modules/objfmts/bin/bin-objfmt.c:1352 #16 0x55772d5827b6 in do_assemble frontends/yasm/yasm.c:546 #17 0x55772d58327c in main frontends/yasm/yasm.c:749 #18 0x7f1cd63ab082 in __libc_start_main ../csu/libc-start.c:308 #19 0x55772d580b9d in _start (/home/root/isap/yasm-1.3.0/yasm+0xa4b9d) 0x602000006ed0 is located 0 bytes inside of 16-byte region [0x602000006ed0,0x602000006ee0) freed by thread T0 here: #0 0x7f1cd668640f in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:122 #1 0x55772d5bd4ae in def_xfree libyasm/xmalloc.c:113 #2 0x55772d5a2f05 in yasm_floatnum_destroy libyasm/floatnum.c:510 #3 0x55772d6892a1 in expr_delete_term libyasm/expr.c:1020 #4 0x55772d6861a8 in expr_simplify_identity libyasm/expr.c:582 #5 0x55772d68711f in expr_level_op libyasm/expr.c:701 #6 0x55772d6887df in expr_level_tree libyasm/expr.c:880 #7 0x55772d688849 in expr_level_tree libyasm/expr.c:886 #8 0x55772d68859d in expr_level_tree libyasm/expr.c:864 #9 0x55772d6889a3 in yasm_expr__level_tree libyasm/expr.c:906 #10 0x55772d647a0e in bin_objfmt_output_value modules/objfmts/bin/bin-objfmt.c:954 #11 0x55772d67c8b6 in bc_data_tobytes libyasm/bc-data.c:226 #12 0x55772d682c9b in yasm_bc_tobytes libyasm/bytecode.c:341 #13 0x55772d647c94 in bin_objfmt_output_bytecode modules/objfmts/bin/bin-objfmt.c:984 #14 0x55772d5ac83a in yasm_section_bcs_traverse libyasm/section.c:637 #15 0x55772d6486ac in bin_objfmt_output_section modules/objfmts/bin/bin-objfmt.c:1082 #16 0x55772d5ac1ad in yasm_object_sections_traverse libyasm/section.c:544 #17 0x55772d64a709 in bin_objfmt_output modules/objfmts/bin/bin-objfmt.c:1352 #18 0x55772d5827b6 in do_assemble frontends/yasm/yasm.c:546 #19 0x55772d58327c in main frontends/yasm/yasm.c:749 #20 0x7f1cd63ab082 in __libc_start_main ../csu/libc-start.c:308 previously allocated by thread T0 here: #0 0x7f1cd6686808 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:144 #1 0x55772d5bd391 in def_xmalloc libyasm/xmalloc.c:69 #2 0x55772d5a1d0b in yasm_floatnum_create libyasm/floatnum.c:314 #3 0x55772d6b4832 in nasm_parser_lex modules/parsers/nasm/nasm-token.re:207 #4 0x55772d5f3269 in parse_expr6 modules/parsers/nasm/nasm-parse.c:1349 #5 0x55772d5f2d5d in parse_expr5 modules/parsers/nasm/nasm-parse.c:1313 #6 0x55772d5f29ea in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #7 0x55772d5f2745 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #8 0x55772d5f2585 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #9 0x55772d5f2453 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #10 0x55772d5f2205 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #11 0x55772d5f2043 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #12 0x55772d5ed7a9 in parse_exp modules/parsers/nasm/nasm-parse.c:608 #13 0x55772d5eb149 in parse_line modules/parsers/nasm/nasm-parse.c:289 #14 0x55772d5eaa1e in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:231 #15 0x55772d5e9aa6 in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #16 0x55772d5e9c43 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #17 0x55772d5824d4 in do_assemble frontends/yasm/yasm.c:519 #18 0x55772d58327c in main frontends/yasm/yasm.c:749 #19 0x7f1cd63ab082 in __libc_start_main ../csu/libc-start.c:308 SUMMARY: AddressSanitizer: heap-use-after-free libyasm/floatnum.c:509 in yasm_floatnum_destroy Shadow bytes around the buggy address: 0x0c047fff8d80: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa 0x0c047fff8d90: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa 0x0c047fff8da0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa 0x0c047fff8db0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa 0x0c047fff8dc0: fa fa fd fa fa fa fd fd fa fa fd fd fa fa 00 00 =>0x0c047fff8dd0: fa fa 02 fa fa fa 00 00 fa fa[fd]fd fa fa 02 fa 0x0c047fff8de0: fa fa 00 00 fa fa 02 fa fa fa 00 00 fa fa 00 00 0x0c047fff8df0: fa fa fd fd fa fa fd fd fa fa fd fd fa fa 00 00 0x0c047fff8e00: fa fa 00 00 fa fa 00 00 fa fa 00 00 fa fa 00 00 0x0c047fff8e10: fa fa fd fd fa fa fd fd fa fa 00 00 fa fa fd fd 0x0c047fff8e20: fa fa 00 00 fa fa 00 00 fa fa fd fd fa fa 00 00 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 Shadow gap: cc ==2673798==ABORTING Thank you for your attention and support. Best regards, Michael Zhang.
heap-use-after-free libyasm/floatnum.c:509 in yasm_floatnum_destroy
https://api.github.com/repos/yasm/yasm/issues/237/comments
0
2023-07-15T11:28:23Z
2023-07-15T11:28:23Z
https://github.com/yasm/yasm/issues/237
1,806,028,408
237
[ "yasm", "yasm" ]
Hello Yasm developers, We recently conducted a fuzzing test on yasm and discovered a heap-buffer-overflow bug. We would like to provide a detailed description of the bug and seek your assistance in addressing it. version: Yasm: 1.3.0 gcc:gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ubuntu: 20.04 command to reproduce: yasm [HBO](https://github.com/shinibufa/crash_seeds/blob/main/yasm/HBO) ASAN report: ================================================================= ==2673369==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60c000000338 at pc 0x5594a92045e4 bp 0x7ffe9b4c82e0 sp 0x7ffe9b4c82d0 READ of size 8 at 0x60c000000338 thread T0 #0 0x5594a92045e3 in expand_mmac_params modules/preprocs/nasm/nasm-pp.c:3977 #1 0x5594a920bbd1 in pp_getline modules/preprocs/nasm/nasm-pp.c:5070 #2 0x5594a91e9719 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:195 #3 0x5594a91de027 in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219 #4 0x5594a91dcaa6 in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #5 0x5594a91dcc43 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #6 0x5594a91754d4 in do_assemble frontends/yasm/yasm.c:519 #7 0x5594a917627c in main frontends/yasm/yasm.c:749 #8 0x7faaddce8082 in __libc_start_main ../csu/libc-start.c:308 #9 0x5594a9173b9d in _start (/home/root/isap/yasm-1.3.0/yasm+0xa4b9d) 0x60c000000338 is located 8 bytes to the left of 128-byte region [0x60c000000340,0x60c0000003c0) allocated by thread T0 here: #0 0x7faaddfc3808 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:144 #1 0x5594a91b0450 in def_xrealloc libyasm/xmalloc.c:99 #2 0x5594a91f55d3 in count_mmac_params modules/preprocs/nasm/nasm-pp.c:1951 #3 0x5594a9207e35 in is_mmacro modules/preprocs/nasm/nasm-pp.c:4553 #4 0x5594a9208d0f in expand_mmacro modules/preprocs/nasm/nasm-pp.c:4673 #5 0x5594a920beef in pp_getline modules/preprocs/nasm/nasm-pp.c:5120 #6 0x5594a91e9719 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:195 #7 0x5594a91de027 in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219 #8 0x5594a91dcaa6 in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #9 0x5594a91dcc43 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #10 0x5594a91754d4 in do_assemble frontends/yasm/yasm.c:519 #11 0x5594a917627c in main frontends/yasm/yasm.c:749 #12 0x7faaddce8082 in __libc_start_main ../csu/libc-start.c:308 SUMMARY: AddressSanitizer: heap-buffer-overflow modules/preprocs/nasm/nasm-pp.c:3977 in expand_mmac_params Shadow bytes around the buggy address: 0x0c187fff8010: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 0x0c187fff8020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c187fff8030: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00 0x0c187fff8040: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 0x0c187fff8050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c187fff8060: fa fa fa fa fa fa fa[fa]00 00 00 00 00 00 00 00 0x0c187fff8070: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 0x0c187fff8080: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c187fff8090: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c187fff80a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c187fff80b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 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 Shadow gap: cc ==2673369==ABORTING Thank you for your attention and support. Best regards, Michael Zhang.
heap-buffer-overflow modules/preprocs/nasm/nasm-pp.c:3977 in expand_mmac_params
https://api.github.com/repos/yasm/yasm/issues/236/comments
0
2023-07-15T11:24:36Z
2023-07-15T11:24:36Z
https://github.com/yasm/yasm/issues/236
1,806,027,134
236
[ "yasm", "yasm" ]
The current latest tag, even it release on 2019, it was created in 2014. The repo still active. (commit from 2 weeks ago). Can you release new version?
Release new version
https://api.github.com/repos/yasm/yasm/issues/235/comments
2
2023-07-12T00:10:54Z
2023-12-12T20:08:11Z
https://github.com/yasm/yasm/issues/235
1,799,944,329
235
[ "yasm", "yasm" ]
# Description While fuzzing yasm, a SEGV occured which was positioned in yasm/libyasm/intnum.c:399:19 in yasm_intnum_copy. This bug may allow attackers to cause a crash or denial of service via a designed crafted files. # Operating system Ubuntu 20.04.6 LTS # ASAN info ``` ./bin/yasm -p gas -f elf32 -g dwarf2 ./out/default/crashes/id\:000035\,sig\:11\,src\:000071\,time\:10629\,execs\:3296\,op\:havoc\,rep\:4 AddressSanitizer:DEADLYSIGNAL ================================================================= ==1770==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x555a0d6a722a bp 0x7fff3af67550 sp 0x7fff3af67530 T0) ==1770==The signal is caused by a READ memory access. ==1770==Hint: address points to the zero page. #0 0x555a0d6a722a in yasm_intnum_copy /AFLplusplus/my_test/yasm/libyasm/intnum.c:399:19 #1 0x555a0d7b66b4 in elf_symtab_write_to_file /AFLplusplus/my_test/yasm/modules/objfmts/elf/elf.c:485:25 #2 0x555a0d7a723b in elf_objfmt_output /AFLplusplus/my_test/yasm/modules/objfmts/elf/elf-objfmt.c:812:23 #3 0x555a0d65e8cd in do_assemble /AFLplusplus/my_test/yasm/frontends/yasm/yasm.c:668:5 #4 0x7feef6770d8f (/lib/x86_64-linux-gnu/libc.so.6+0x29d8f) (BuildId: 69389d485a9793dbe873f0ea2c93e02efaa9aa3d) #5 0x7feef6770e3f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x29e3f) (BuildId: 69389d485a9793dbe873f0ea2c93e02efaa9aa3d) #6 0x555a0d58e004 in _start (/AFLplusplus/my_test/fuzz_yasm/bin/yasm+0x183004) (BuildId: 74b4f28840ac06c5) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /AFLplusplus/my_test/yasm/libyasm/intnum.c:399:19 in yasm_intnum_copy ==1770==ABORTING ``` # Steps to Reproduce `./yasm -p gas -f elf32 -g dwarf2 $FILE ` # Poc https://github.com/ChanStormstout/Pocs/blob/master/yasm_POC/out/default/crashes/id%3A000035%2Csig%3A11%2Csrc%3A000071%2Ctime%3A10629%2Cexecs%3A3296%2Cop%3Ahavoc%2Crep%3A4
SEGV in yasm/libyasm/intnum.c's function :yasm_intnum_copy
https://api.github.com/repos/yasm/yasm/issues/233/comments
0
2023-06-29T13:07:01Z
2023-06-30T15:08:56Z
https://github.com/yasm/yasm/issues/233
1,780,786,529
233
[ "yasm", "yasm" ]
It seems that yasm's `-l` (listing) option does not include bytes for a `rep` prefix if the `rep` is on the same line as the affected `stos`. ## Steps to reproduce Create `hello.S`: ``` .code64 rep ; stosq ``` Run: ``` $ yasm -p gas -L nasm -l hello.list hello.S ``` ## Observed output `hello.list`: ``` 1 .code64 2 00000001 48AB rep ; stosq 3 ``` `hello` (output file hex dump): ``` 00000000 f3 48 ab |.H.| ``` Note that `F3` is missing from `hello.list`. ## Expected output `hello.list`: ``` 1 .code64 2 00000000 F348AB rep ; stosq 3 ``` `hello` (output file hex dump): ``` 00000000 f3 48 ab |.H.| ``` ## More information This bug does not happen if the `rep` and the `stos` are on separate lines: ``` .code64 rep stosq ``` ``` 1 .code64 2 00000000 F3 rep 3 00000001 48AB stosq 4 ``` I am using yasm version 1.3.0.
listing omits bytes of 'rep' prefix if on same line
https://api.github.com/repos/yasm/yasm/issues/230/comments
0
2023-05-31T01:39:05Z
2023-05-31T01:39:05Z
https://github.com/yasm/yasm/issues/230
1,733,245,762
230
[ "yasm", "yasm" ]
cd tools/python-yasm/ python3 setup.py build Traceback (most recent call last): File "setup.py", line 81, in <module> opts = ReadSetup("python-setup.txt") File "setup.py", line 36, in ReadSetup return dict(line.split('=', 1) for line in open(filename)) FileNotFoundError: [Errno 2] No such file or directory: 'python-setup.txt'
missing python-setup.txt
https://api.github.com/repos/yasm/yasm/issues/229/comments
0
2023-05-28T01:55:48Z
2023-05-28T01:55:48Z
https://github.com/yasm/yasm/issues/229
1,729,082,792
229
[ "yasm", "yasm" ]
# At first, I have built yasm: installdir=/usr/local git clone yasm mkdir mybuild && cd mybuild cmake -DCMAKE_INSTALL_PREFIX="$installdir" .. make ctest # No tests were found!!! make install cd .. yasm --version # yasm-1.3.0 # to build x86 plugin - ok: pushd plugins/x86 mkdir mybuild cd mybuild cmake .. make popd # to build dbg plugin - error: pushd plugins/dbg/ mkdir mybuild cd mybuild cmake .. make # error: /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:165:5: warning: initialization of ‘unsigned char’ from ‘const char **’ makes integer from pointer without a cast [-Wint-conversion] 165 | dbg_objfmt_dbgfmt_keywords, | ^~~~~~~~~~~~~~~~~~~~~~~~~~ /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:165:5: note: (near initialization for ‘yasm_dbg_LTX_objfmt.id_at_ok’) /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:165:5: error: initializer element is not computable at load time /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:165:5: note: (near initialization for ‘yasm_dbg_LTX_objfmt.id_at_ok’) /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:166:5: warning: initialization of ‘const char **’ from incompatible pointer type ‘char *’ [-Wincompatible-pointer-types] 166 | "null", | ^~~~~~ /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:166:5: note: (near initialization for ‘yasm_dbg_LTX_objfmt.dbgfmt_keywords’) /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:169:5: warning: initialization of ‘const yasm_stdmac *’ {aka ‘const struct yasm_stdmac *’} from incompatible pointer type ‘yasm_objfmt * (*)(yasm_object *)’ {aka ‘struct yasm_objfmt * (*)(struct yasm_object *)’} [-Wincompatible-pointer-types] 169 | dbg_objfmt_create, | ^~~~~~~~~~~~~~~~~ /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:169:5: note: (near initialization for ‘yasm_dbg_LTX_objfmt.stdmacs’) /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:170:5: warning: initialization of ‘yasm_objfmt * (*)(yasm_object *)’ {aka ‘struct yasm_objfmt * (*)(struct yasm_object *)’} from incompatible pointer type ‘void (*)(yasm_object *, FILE *, int, yasm_errwarns *)’ {aka ‘void (*)(struct yasm_object *, struct _IO_FILE *, int, struct yasm_errwarns *)’} [-Wincompatible-pointer-types] 170 | dbg_objfmt_output, | ^~~~~~~~~~~~~~~~~ /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:170:5: note: (near initialization for ‘yasm_dbg_LTX_objfmt.create’) /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:171:5: warning: initialization of ‘void (*)(yasm_object *, FILE *, int, yasm_errwarns *)’ {aka ‘void (*)(struct yasm_object *, struct _IO_FILE *, int, struct yasm_errwarns *)’} from incompatible pointer type ‘void (*)(yasm_objfmt *)’ {aka ‘void (*)(struct yasm_objfmt *)’} [-Wincompatible-pointer-types] 171 | dbg_objfmt_destroy, | ^~~~~~~~~~~~~~~~~~ /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:171:5: note: (near initialization for ‘yasm_dbg_LTX_objfmt.output’) /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:172:5: warning: initialization of ‘void (*)(yasm_objfmt *)’ {aka ‘void (*)(struct yasm_objfmt *)’} from incompatible pointer type ‘yasm_section * (*)(yasm_object *)’ {aka ‘struct yasm_section * (*)(struct yasm_object *)’} [-Wincompatible-pointer-types] 172 | dbg_objfmt_add_default_section, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:172:5: note: (near initialization for ‘yasm_dbg_LTX_objfmt.destroy’) /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:173:5: warning: initialization of ‘yasm_section * (*)(yasm_object *)’ {aka ‘struct yasm_section * (*)(struct yasm_object *)’} from incompatible pointer type ‘yasm_section * (*)(yasm_object *, yasm_valparamhead *, yasm_valparamhead *, long unsigned int)’ {aka ‘struct yasm_section * (*)(struct yasm_object *, struct yasm_valparamhead *, struct yasm_valparamhead *, long unsigned int)’} [-Wincompatible-pointer-types] 173 | dbg_objfmt_section_switch, | ^~~~~~~~~~~~~~~~~~~~~~~~~ /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:173:5: note: (near initialization for ‘yasm_dbg_LTX_objfmt.add_default_section’) /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:174:5: warning: initialization of ‘void (*)(yasm_section *, long unsigned int)’ {aka ‘void (*)(struct yasm_section *, long unsigned int)’} from incompatible pointer type ‘yasm_symrec * (*)(yasm_object *, const char *, const char *)’ {aka ‘struct yasm_symrec * (*)(struct yasm_object *, const char *, const char *)’} [-Wincompatible-pointer-types] 174 | dbg_objfmt_get_special_sym | ^~~~~~~~~~~~~~~~~~~~~~~~~~ /mnt/Git/build/yasm/plugins/dbg/dbg-objfmt.c:174:5: note: (near initialization for ‘yasm_dbg_LTX_objfmt.init_new_section’) make[2]: *** [CMakeFiles/dbgmod.dir/build.make:90: CMakeFiles/dbgmod.dir/dbg-objfmt.o] Ошибка 1 make[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/dbgmod.dir/all] Ошибка 2 make: *** [Makefile:91: all] Ошибка 2
plugins build error
https://api.github.com/repos/yasm/yasm/issues/228/comments
0
2023-05-28T01:26:34Z
2023-05-28T01:26:34Z
https://github.com/yasm/yasm/issues/228
1,729,070,374
228
[ "yasm", "yasm" ]
# There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:3570 in do_directive ## asan info: ``` AddressSanitizer:DEADLYSIGNAL ================================================================= ==1433063==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x55736a1a1cff bp 0x7fff4d5cbf50 sp 0x7fff4d5cba60 T0) ==1433063==The signal is caused by a READ memory access. ==1433063==Hint: address points to the zero page. #0 0x55736a1a1cfe in do_directive modules/preprocs/nasm/nasm-pp.c:3570 #1 0x55736a1ac446 in pp_getline modules/preprocs/nasm/nasm-pp.c:5083 #2 0x55736a189c61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198 #3 0x55736a17e4ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219 #4 0x55736a17cf6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #5 0x55736a17d109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #6 0x55736a1154d4 in do_assemble frontends/yasm/yasm.c:521 #7 0x55736a116281 in main frontends/yasm/yasm.c:753 #8 0x7fbf8492d082 in __libc_start_main ../csu/libc-start.c:308 #9 0x55736a113b9d in _start (/root/target/latest/20230404/yasm/build_asan/bin/yasm+0xa5b9d) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV modules/preprocs/nasm/nasm-pp.c:3570 in do_directive ==1433063==ABORTING ``` ## Command Input: ./yasm poc-file [poc-file.zip](https://github.com/yasm/yasm/files/11253195/poc-file.zip) poc-file is attached. ## Environment OS: Ubuntu 20.04.1 yasm: 1.3.0.55.g101bc (git clone [[email protected]](mailto:[email protected]):yasm/yasm.git , and compile it) compile yasm with asan: ./autogen.sh make distclean ./configure --prefix=$PWD/build_asan make CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" make install
There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:3570 in do_directive
https://api.github.com/repos/yasm/yasm/issues/222/comments
1
2023-04-17T16:48:59Z
2024-03-22T11:50:46Z
https://github.com/yasm/yasm/issues/222
1,671,589,854
222
[ "yasm", "yasm" ]
# There exists heap-use-after-free in yasm/modules/preprocs/nasm/nasm-pp.c:3878 in expand_mmac_params ## asan info: ``` ==708699==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000012a8 at pc 0x55647c385147 bp 0x7ffe09f5d870 sp 0x7ffe09f5d860 READ of size 8 at 0x60e0000012a8 thread T0 #0 0x55647c385146 in expand_mmac_params modules/preprocs/nasm/nasm-pp.c:3878 #1 0x55647c38d436 in pp_getline modules/preprocs/nasm/nasm-pp.c:5078 #2 0x55647c36ac61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198 #3 0x55647c35f4ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219 #4 0x55647c35df6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #5 0x55647c35e109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #6 0x55647c2f64d4 in do_assemble frontends/yasm/yasm.c:521 #7 0x55647c2f7281 in main frontends/yasm/yasm.c:753 #8 0x7fc63b1af082 in __libc_start_main ../csu/libc-start.c:308 #9 0x55647c2f4b9d in _start (/root/target/yasm/build_asan/bin/yasm+0xa5b9d) 0x60e0000012a8 is located 8 bytes inside of 160-byte region [0x60e0000012a0,0x60e000001340) freed by thread T0 here: #0 0x7fc63b48a40f in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:122 #1 0x55647c331974 in def_xfree libyasm/xmalloc.c:113 #2 0x55647c370a59 in free_mmacro modules/preprocs/nasm/nasm-pp.c:1163 #3 0x55647c38cc0a in pp_getline modules/preprocs/nasm/nasm-pp.c:5009 #4 0x55647c36ac61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198 #5 0x55647c35f4ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219 #6 0x55647c35df6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #7 0x55647c35e109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #8 0x55647c2f64d4 in do_assemble frontends/yasm/yasm.c:521 #9 0x55647c2f7281 in main frontends/yasm/yasm.c:753 #10 0x7fc63b1af082 in __libc_start_main ../csu/libc-start.c:308 previously allocated by thread T0 here: #0 0x7fc63b48a808 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cc:144 #1 0x55647c331857 in def_xmalloc libyasm/xmalloc.c:69 #2 0x55647c37ffc8 in do_directive modules/preprocs/nasm/nasm-pp.c:3211 #3 0x55647c38d446 in pp_getline modules/preprocs/nasm/nasm-pp.c:5083 #4 0x55647c36ac61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198 #5 0x55647c35f4ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219 #6 0x55647c35df6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #7 0x55647c35e109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #8 0x55647c2f64d4 in do_assemble frontends/yasm/yasm.c:521 #9 0x55647c2f7281 in main frontends/yasm/yasm.c:753 #10 0x7fc63b1af082 in __libc_start_main ../csu/libc-start.c:308 SUMMARY: AddressSanitizer: heap-use-after-free modules/preprocs/nasm/nasm-pp.c:3878 in expand_mmac_params Shadow bytes around the buggy address: 0x0c1c7fff8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8230: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd 0x0c1c7fff8240: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa =>0x0c1c7fff8250: fa fa fa fa fd[fd]fd fd fd fd fd fd fd fd fd fd 0x0c1c7fff8260: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa 0x0c1c7fff8270: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c1c7fff8280: fd fd fd fd fa fa fa fa fa fa fa fa fd fd fd fd 0x0c1c7fff8290: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c1c7fff82a0: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00 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 Shadow gap: cc ==708699==ABORTING ``` ## Command Input: ./yasm poc-file [poc-file.zip](https://github.com/yasm/yasm/files/11253102/poc-file.zip) poc-file is attached. ## Environment OS: Ubuntu 20.04.1 yasm: 1.3.0.55.g101bc (git clone [[email protected]](mailto:[email protected]):yasm/yasm.git , and compile it) compile yasm with asan: ./autogen.sh make distclean ./configure --prefix=$PWD/build_asan make CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" make install
There exists heap-use-after-free in yasm/modules/preprocs/nasm/nasm-pp.c:3878 in expand_mmac_params
https://api.github.com/repos/yasm/yasm/issues/221/comments
1
2023-04-17T16:39:42Z
2024-03-22T11:51:42Z
https://github.com/yasm/yasm/issues/221
1,671,576,475
221
[ "yasm", "yasm" ]
# There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:4008 in expand_mmac_params ## asan info: ``` AddressSanitizer:DEADLYSIGNAL ================================================================= ==3645333==ERROR: AddressSanitizer: SEGV on unknown address 0x60bcf518f500 (pc 0x562c742f3049 bp 0x7ffc6fb07330 sp 0x7ffc6fb07200 T0) ==3645333==The signal is caused by a READ memory access. #0 0x562c742f3048 in expand_mmac_params modules/preprocs/nasm/nasm-pp.c:4008 #1 0x562c742ead70 in do_directive modules/preprocs/nasm/nasm-pp.c:2950 #2 0x562c742fa446 in pp_getline modules/preprocs/nasm/nasm-pp.c:5083 #3 0x562c742d7c61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198 #4 0x562c742cc4ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219 #5 0x562c742caf6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #6 0x562c742cb109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #7 0x562c742634d4 in do_assemble frontends/yasm/yasm.c:521 #8 0x562c74264281 in main frontends/yasm/yasm.c:753 #9 0x7f44d85c0082 in __libc_start_main ../csu/libc-start.c:308 #10 0x562c74261b9d in _start (/root/target/yasm/build_asan/bin/yasm+0xa5b9d) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV modules/preprocs/nasm/nasm-pp.c:4008 in expand_mmac_params ==3645333==ABORTING ``` ## Command Input: ./yasm poc-file [poc-file.zip](https://github.com/yasm/yasm/files/11252936/poc-file.zip) poc-file is attached. ## Environment OS: Ubuntu 20.04.1 yasm: 1.3.0.55.g101bc (git clone [[email protected]](mailto:[email protected]):yasm/yasm.git , and compile it) compile yasm with asan: ./autogen.sh make distclean ./configure --prefix=$PWD/build_asan make CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" make install You can also reproduce it without ASAN , don't set CFLAGS and CXXFLAGS and directly use GDB. ## GDB results: ![image](https://user-images.githubusercontent.com/56296073/232547752-2d704d5b-e622-4ec3-9673-14dbbf96c43e.png) we use "p mac->params[n]"but can't access memory. SEGV happens.
There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:4008 in expand_mmac_params
https://api.github.com/repos/yasm/yasm/issues/220/comments
1
2023-04-17T16:18:19Z
2024-03-22T11:52:08Z
https://github.com/yasm/yasm/issues/220
1,671,545,980
220
[ "yasm", "yasm" ]
# There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:2134/if_condition ## ASAN info: ``` AddressSanitizer:DEADLYSIGNAL ================================================================= ==2586705==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x56354074e373 bp 0x7ffcc98771d0 sp 0x7ffcc9876f90 T0) ==2586705==The signal is caused by a READ memory access. ==2586705==Hint: address points to the zero page. #0 0x56354074e372 in if_condition modules/preprocs/nasm/nasm-pp.c:2134 #1 0x5635407538e1 in do_directive modules/preprocs/nasm/nasm-pp.c:2907 #2 0x563540763446 in pp_getline modules/preprocs/nasm/nasm-pp.c:5083 #3 0x563540740c61 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198 #4 0x5635407354ed in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219 #5 0x563540733f6c in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #6 0x563540734109 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #7 0x5635406cc4d4 in do_assemble frontends/yasm/yasm.c:521 #8 0x5635406cd281 in main frontends/yasm/yasm.c:753 #9 0x7fcc00d56082 in __libc_start_main ../csu/libc-start.c:308 #10 0x5635406cab9d in _start (/root/target/latest/20230404/yasm/build_asan/bin/yasm+0xa5b9d) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV modules/preprocs/nasm/nasm-pp.c:2134 in if_condition ==2586705==ABORTING ``` ## Command Input: ./yasm poc-file [poc-file.zip](https://github.com/yasm/yasm/files/11250876/poc-file.zip) poc-file is attached. ## Environment OS: Ubuntu 20.04.1 yasm: 1.3.0.55.g101bc (git clone [email protected]:yasm/yasm.git , and compile it) compile yasm with asan: ./autogen.sh make distclean ./configure --prefix=`pwd`/buildasan make CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" make install You can also reproduce it without ASAN , don't set CFLAGS and CXXFLAGS and directly use GDB. ## GDB results: ![image](https://user-images.githubusercontent.com/56296073/232506327-c7af26df-8a1a-41c5-b045-a98291e9992b.png) Here we use "p tline->next"but can't access memory. SEGV happens.
There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:2134/if_condition
https://api.github.com/repos/yasm/yasm/issues/219/comments
0
2023-04-17T14:00:21Z
2023-04-18T03:20:34Z
https://github.com/yasm/yasm/issues/219
1,671,254,497
219
[ "yasm", "yasm" ]
# stack-overflow yasm/modules/parsers/nasm/nasm-parse.c:1303 in parse_expr5 ## project address https://github.com/yasm/yasm ## info OS:Ubuntu20.04 TLS Build: ./autogen.sh && make distclean && CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared && make -j && make install ## Poc https://github.com/z1r00/fuzz_vuln/blob/main/yasm/stack-overflow/parse_expr5/id:000456%2Csig:06%2Csrc:000215%2B005032%2Cop:splice%2Crep:64 ## ASAN Info ```c ./yasm id:000456,sig:06,src:000215+005032,op:splice,rep:64 yasm: file name already has no extension: output will be in `yasm.out' AddressSanitizer:DEADLYSIGNAL ================================================================= ==3060203==ERROR: AddressSanitizer: stack-overflow on address 0x7ffebdf10ff8 (pc 0x00000063de80 bp 0x7ffebdf11120 sp 0x7ffebdf11000 T0) #0 0x63de80 in nasm_parser_lex /home/z1r0/fuzzing/yasm/yasm/./modules/parsers/nasm/nasm-token.re:117 #1 0x57d60d in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1400:13 #2 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #3 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #4 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #5 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #6 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #7 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #8 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #9 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #10 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #11 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #12 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #13 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #14 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #15 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #16 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #17 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #18 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #19 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #20 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #21 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #22 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #23 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #24 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #25 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #26 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #27 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #28 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #29 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #30 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #31 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #32 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #33 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #34 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #35 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #36 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #37 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #38 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #39 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #40 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #41 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #42 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #43 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #44 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #45 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #46 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #47 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #48 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #49 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #50 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #51 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #52 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #53 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #54 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #55 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #56 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #57 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #58 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #59 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #60 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #61 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #62 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #63 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #64 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #65 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #66 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #67 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #68 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #69 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #70 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #71 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #72 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #73 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #74 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #75 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #76 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #77 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #78 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #79 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #80 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #81 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #82 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #83 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #84 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #85 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #86 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #87 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #88 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #89 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #90 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #91 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #92 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #93 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #94 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #95 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #96 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #97 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #98 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #99 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #100 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #101 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #102 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #103 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #104 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #105 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #106 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #107 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #108 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #109 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #110 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #111 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #112 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #113 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #114 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #115 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #116 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #117 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #118 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #119 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #120 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #121 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #122 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #123 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #124 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #125 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #126 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #127 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #128 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #129 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #130 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #131 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #132 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #133 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #134 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #135 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #136 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #137 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #138 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #139 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #140 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #141 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #142 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #143 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #144 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #145 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #146 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #147 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #148 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #149 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #150 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #151 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #152 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #153 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #154 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #155 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #156 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #157 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #158 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #159 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #160 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #161 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #162 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #163 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #164 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #165 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #166 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #167 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #168 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #169 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #170 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #171 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #172 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #173 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #174 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #175 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #176 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #177 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #178 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #179 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #180 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #181 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #182 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #183 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #184 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #185 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #186 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #187 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #188 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #189 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #190 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #191 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #192 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #193 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #194 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #195 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #196 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #197 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #198 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #199 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #200 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #201 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #202 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #203 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #204 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #205 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #206 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #207 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #208 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #209 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #210 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #211 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #212 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #213 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #214 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #215 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #216 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #217 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #218 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #219 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #220 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #221 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #222 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #223 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #224 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #225 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #226 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #227 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #228 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #229 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #230 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #231 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #232 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #233 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #234 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #235 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #236 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #237 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #238 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #239 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #240 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #241 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #242 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #243 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #244 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #245 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #246 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #247 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #248 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 SUMMARY: AddressSanitizer: stack-overflow /home/z1r0/fuzzing/yasm/yasm/./modules/parsers/nasm/nasm-token.re:117 in nasm_parser_lex ==3060203==ABORTING ``` ## Reference https://github.com/z1r00/fuzz_vuln/blob/main/yasm/stack-overflow/parse_expr5/readme.md
stack-overflow yasm/modules/parsers/nasm/nasm-parse.c:1303 in parse_expr5
https://api.github.com/repos/yasm/yasm/issues/218/comments
1
2023-03-31T08:27:44Z
2024-03-22T11:55:05Z
https://github.com/yasm/yasm/issues/218
1,648,929,873
218
[ "yasm", "yasm" ]
# stack-overflow yasm/modules/parsers/nasm/nasm-parse.c:1235 in parse_expr1 ## project address https://github.com/yasm/yasm ## info OS:Ubuntu20.04 TLS Build: ./autogen.sh && make distclean && CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared && make -j && make install ## Poc https://github.com/z1r00/fuzz_vuln/blob/main/yasm/stack-overflow/parse_expr1/id:000206%2Csig:06%2Csrc:007018%2B003531%2Cop:splice%2Crep:32 ## ASAN Info ```c ./yasm id:000206,sig:06,src:007018+003531,op:splice,rep:32 yasm: file name already has no extension: output will be in `yasm.out' AddressSanitizer:DEADLYSIGNAL ================================================================= ==2596551==ERROR: AddressSanitizer: stack-overflow on address 0x7ffe5cfb8fe8 (pc 0x00000057e8cb bp 0x7ffe5cfb9040 sp 0x7ffe5cfb8ff0 T0) #0 0x57e8cb in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1235 #1 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #2 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #3 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #4 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #5 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #6 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #7 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #8 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #9 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #10 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #11 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #12 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #13 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #14 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #15 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #16 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #17 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #18 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #19 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #20 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #21 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #22 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #23 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #24 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #25 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #26 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #27 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #28 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #29 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #30 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #31 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #32 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #33 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #34 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #35 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #36 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #37 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #38 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #39 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #40 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #41 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #42 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #43 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #44 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #45 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #46 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #47 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #48 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #49 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #50 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #51 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #52 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #53 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #54 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #55 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #56 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #57 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #58 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #59 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #60 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #61 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #62 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #63 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #64 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #65 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #66 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #67 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #68 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #69 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #70 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #71 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #72 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #73 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #74 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #75 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #76 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #77 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #78 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #79 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #80 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #81 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #82 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #83 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #84 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #85 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #86 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #87 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #88 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #89 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #90 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #91 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #92 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #93 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #94 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #95 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #96 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #97 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #98 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #99 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #100 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #101 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #102 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #103 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #104 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #105 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #106 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #107 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #108 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #109 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #110 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #111 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #112 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #113 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #114 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #115 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #116 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #117 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #118 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #119 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #120 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #121 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #122 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #123 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #124 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #125 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #126 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #127 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #128 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #129 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #130 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #131 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #132 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #133 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #134 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #135 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #136 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #137 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #138 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #139 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #140 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #141 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #142 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #143 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #144 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #145 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #146 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #147 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #148 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #149 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #150 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #151 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #152 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #153 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #154 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #155 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #156 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #157 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #158 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #159 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #160 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #161 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #162 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #163 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #164 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #165 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #166 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #167 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #168 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #169 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #170 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #171 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #172 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #173 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #174 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #175 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #176 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #177 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #178 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #179 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #180 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #181 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #182 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #183 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #184 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #185 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #186 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #187 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #188 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #189 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #190 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #191 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #192 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #193 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #194 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #195 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #196 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #197 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #198 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #199 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #200 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #201 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #202 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #203 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #204 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #205 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #206 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #207 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #208 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #209 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #210 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #211 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #212 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #213 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #214 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #215 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #216 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #217 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #218 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #219 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #220 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #221 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #222 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #223 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #224 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #225 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #226 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #227 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #228 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #229 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #230 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #231 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #232 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #233 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #234 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #235 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #236 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #237 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #238 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #239 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 #240 0x57ef2f in parse_expr4 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1277:9 #241 0x57ecbc in parse_expr3 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1249:9 #242 0x57eacc in parse_expr2 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1242:5 #243 0x57e8dc in parse_expr1 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1236:5 #244 0x57d29c in parse_expr0 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1230:5 #245 0x57d0ac in parse_bexpr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1224:5 #246 0x57ceb6 in parse_expr /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1215:13 #247 0x57d62e in parse_expr6 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1401:17 #248 0x57f13f in parse_expr5 /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1305:9 SUMMARY: AddressSanitizer: stack-overflow /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1235 in parse_expr1 ==2596551==ABORTING ``` ## Reference https://github.com/z1r00/fuzz_vuln/blob/main/yasm/stack-overflow/parse_expr1/readme.md
stack-overflow yasm/modules/parsers/nasm/nasm-parse.c:1235 in parse_expr1
https://api.github.com/repos/yasm/yasm/issues/217/comments
1
2023-03-31T08:22:30Z
2024-03-22T11:56:45Z
https://github.com/yasm/yasm/issues/217
1,648,921,272
217
[ "yasm", "yasm" ]
# SEGV yasm/modules/preprocs/nasm/nasm-pp.c in delete_Token ## project address https://github.com/yasm/yasm ## info OS:Ubuntu20.04 TLS Build: ./autogen.sh && make distclean && CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared && make -j && make install ## Poc https://github.com/z1r00/fuzz_vuln/blob/main/yasm/segv/delete_Token/id:000176%2Csig:06%2Csrc:008442%2B007750%2Cop:splice%2Crep:128 ## ASAN Info ```c ./yasm id:000176,sig:06,src:008442+007750,op:splice,rep:128 yasm: file name already has no extension: output will be in `yasm.out' AddressSanitizer:DEADLYSIGNAL ================================================================= ==3784849==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x0000005994b7 bp 0x7ffd44e1e310 sp 0x7ffd44e1de80 T0) ==3784849==The signal is caused by a READ memory access. ==3784849==Hint: address points to the zero page. #0 0x5994b7 in delete_Token /home/z1r0/fuzzing/yasm/yasm/modules/preprocs/nasm/nasm-pp.c #1 0x5994b7 in expand_macros_in_string /home/z1r0/fuzzing/yasm/yasm/modules/preprocs/nasm/nasm-pp.c:2317:16 #2 0x5994b7 in do_directive /home/z1r0/fuzzing/yasm/yasm/modules/preprocs/nasm/nasm-pp.c:2873:17 #3 0x58994f in pp_getline /home/z1r0/fuzzing/yasm/yasm/modules/preprocs/nasm/nasm-pp.c:5083:13 #4 0x58291c in nasm_preproc_get_line /home/z1r0/fuzzing/yasm/yasm/modules/preprocs/nasm/nasm-preproc.c:198:12 #5 0x578570 in nasm_parser_parse /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:219:13 #6 0x577618 in nasm_do_parse /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parser.c:66:5 #7 0x577618 in nasm_parser_do_parse /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parser.c:83:5 #8 0x4c6eae in do_assemble /home/z1r0/fuzzing/yasm/yasm/frontends/yasm/yasm.c:521:5 #9 0x4c6eae in main /home/z1r0/fuzzing/yasm/yasm/frontends/yasm/yasm.c:753:12 #10 0x7f150c316082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 #11 0x41c47d in _start (/home/z1r0/fuzzing/yasm/yasm/yasm+0x41c47d) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/z1r0/fuzzing/yasm/yasm/modules/preprocs/nasm/nasm-pp.c in delete_Token ==3784849==ABORTING ``` ## Reference https://github.com/z1r00/fuzz_vuln/blob/main/yasm/segv/delete_Token/readme.md
SEGV yasm/modules/preprocs/nasm/nasm-pp.c in delete_Token
https://api.github.com/repos/yasm/yasm/issues/216/comments
13
2023-03-31T08:02:18Z
2024-03-22T12:02:52Z
https://github.com/yasm/yasm/issues/216
1,648,877,295
216
[ "yasm", "yasm" ]
# SEGV yasm/libyasm/expr.c:87:44 in yasm_expr_create ## project address https://github.com/yasm/yasm ## info OS:Ubuntu20.04 TLS Build: ./autogen.sh && make distclean && CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared && make -j && make install ## Poc https://github.com/z1r00/fuzz_vuln/blob/main/yasm/segv/yasm_expr_create/id:000051%2Csig:06%2Csrc:008025%2Cop:havoc%2Crep:32 ## ASAN Info ```c ./yasm id:000051,sig:06,src:008025,op:havoc,rep:32 yasm: file name already has no extension: output will be in `yasm.out' AddressSanitizer:DEADLYSIGNAL ================================================================= ==3310123==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x00000060db46 bp 0x7ffd285ed390 sp 0x7ffd285ed320 T0) ==3310123==The signal is caused by a READ memory access. ==3310123==Hint: address points to the zero page. #0 0x60db46 in yasm_expr_create /home/z1r0/fuzzing/yasm/yasm/libyasm/expr.c:87:44 #1 0x57c34f in nasm_parser_directive /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1597:17 #2 0x579361 in parse_line /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:377:17 #3 0x579361 in nasm_parser_parse /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:231:18 #4 0x577618 in nasm_do_parse /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parser.c:66:5 #5 0x577618 in nasm_parser_do_parse /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parser.c:83:5 #6 0x4c6eae in do_assemble /home/z1r0/fuzzing/yasm/yasm/frontends/yasm/yasm.c:521:5 #7 0x4c6eae in main /home/z1r0/fuzzing/yasm/yasm/frontends/yasm/yasm.c:753:12 #8 0x7f764ee43082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 #9 0x41c47d in _start (/home/z1r0/fuzzing/yasm/yasm/yasm+0x41c47d) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/z1r0/fuzzing/yasm/yasm/libyasm/expr.c:87:44 in yasm_expr_create ==3310123==ABORTING ```
SEGV yasm/libyasm/expr.c:87:44 in yasm_expr_create
https://api.github.com/repos/yasm/yasm/issues/215/comments
1
2023-03-31T07:56:32Z
2024-03-21T12:41:09Z
https://github.com/yasm/yasm/issues/215
1,648,868,122
215
[ "yasm", "yasm" ]
# stack-buffer-overflow yasm/yasm+0x43b466 in vsprintf ## project address https://github.com/yasm/yasm ## info OS:Ubuntu20.04 TLS Build: ./autogen.sh && make distclean && CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared && make -j && make install ## Poc https://github.com/z1r00/fuzz_vuln/blob/main/yasm/stack-buffer-overflow/yasm/id:000055%2Csig:06%2Csrc:008089%2B007532%2Cop:splice%2Crep:128 ## ASAN Info ```c ./yasm id:000055,sig:06,src:008089+007532,op:splice,rep:128 yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==1107138==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fffb43ff890 at pc 0x00000043b467 bp 0x7fffb43ff760 sp 0x7fffb43feef8 WRITE of size 21 at 0x7fffb43ff890 thread T0 #0 0x43b466 in vsprintf (/home/z1r0/fuzzing/yasm/yasm/yasm+0x43b466) #1 0x43c3f3 in sprintf (/home/z1r0/fuzzing/yasm/yasm/yasm+0x43c3f3) #2 0x54e503 in x86_dir_cpu /home/z1r0/fuzzing/yasm/yasm/modules/arch/x86/x86arch.c:169:17 #3 0x539e14 in yasm_object_directive /home/z1r0/fuzzing/yasm/yasm/libyasm/section.c:377:5 #4 0x57bfe2 in nasm_parser_directive /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:1569:10 #5 0x579361 in parse_line /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:377:17 #6 0x579361 in nasm_parser_parse /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parse.c:231:18 #7 0x577618 in nasm_do_parse /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parser.c:66:5 #8 0x577618 in nasm_parser_do_parse /home/z1r0/fuzzing/yasm/yasm/modules/parsers/nasm/nasm-parser.c:83:5 #9 0x4c6eae in do_assemble /home/z1r0/fuzzing/yasm/yasm/frontends/yasm/yasm.c:521:5 #10 0x4c6eae in main /home/z1r0/fuzzing/yasm/yasm/frontends/yasm/yasm.c:753:12 #11 0x7f833dc86082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 #12 0x41c47d in _start (/home/z1r0/fuzzing/yasm/yasm/yasm+0x41c47d) Address 0x7fffb43ff890 is located in stack of thread T0 at offset 48 in frame #0 0x54e38f in x86_dir_cpu /home/z1r0/fuzzing/yasm/yasm/modules/arch/x86/x86arch.c:153 This frame has 1 object(s): [32, 48) 'strcpu' (line 168) <== Memory access at offset 48 overflows this variable HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-buffer-overflow (/home/z1r0/fuzzing/yasm/yasm/yasm+0x43b466) in vsprintf Shadow bytes around the buggy address: 0x100076877ec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100076877ed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100076877ee0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100076877ef0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100076877f00: 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 =>0x100076877f10: 00 00[f3]f3 00 00 00 00 00 00 00 00 00 00 00 00 0x100076877f20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100076877f30: f1 f1 f1 f1 f8 f3 f3 f3 00 00 00 00 00 00 00 00 0x100076877f40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100076877f50: 00 00 00 00 f1 f1 f1 f1 00 00 f2 f2 f8 f8 f2 f2 0x100076877f60: f8 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 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 Shadow gap: cc ==1107138==ABORTING ``` # Reference https://github.com/z1r00/fuzz_vuln/blob/main/yasm/stack-buffer-overflow/yasm/readmd.md
stack-buffer-overflow yasm/yasm+0x43b466 in vsprintf
https://api.github.com/repos/yasm/yasm/issues/214/comments
1
2023-03-30T13:06:13Z
2024-03-21T12:42:39Z
https://github.com/yasm/yasm/issues/214
1,647,586,741
214
[ "yasm", "yasm" ]
An attempted compilation of v1.3.0 via EasyBuild on a machine with the Intel Xeon Platinum 8352Y CPU processor resulted in: ./genmacro win64-nasm.c win64_nasm_stdmac ./modules/objfmts/coff/win64-nasm.mac ./genmacro win64-gas.c win64_gas_stdmac ./modules/objfmts/coff/win64-gas.mac ./genstring license_msg license.c ./COPYING ./genmacro nasm-version.c nasm_version_mac version.mac fail to map group of size 2 for tab size 512 make: *** [Makefile:4155: gas-token.c] Segmentation fault (core dumped) make: *** Deleting file 'gas-token.c' make: *** Waiting for unfinished jobs.... make: *** [Makefile:4158: nasm-token.c] Segmentation fault (core dumped) make: *** Deleting file 'nasm-token.c' (at easybuild/tools/run.py:643 in parse_cmd_output This problem didn't occur on an 8352Y CPU with 32 cores and 1 thread per core, but is occurring on this CPU with 32 cores and 2 threads per core. S. Baum System Administrator TAMU HPRC
Segfault on Intel Xeon Platinum 8352Y CPU
https://api.github.com/repos/yasm/yasm/issues/213/comments
0
2023-03-29T14:35:48Z
2023-03-29T14:35:48Z
https://github.com/yasm/yasm/issues/213
1,645,951,960
213
[ "yasm", "yasm" ]
null
Documentation doesn't explain how to run tests
https://api.github.com/repos/yasm/yasm/issues/212/comments
0
2023-03-12T02:05:55Z
2023-03-12T02:05:55Z
https://github.com/yasm/yasm/issues/212
1,620,206,094
212
[ "yasm", "yasm" ]
The last release was in 2014, and there were a lot of commits up until 2022.
Plans to make a release?
https://api.github.com/repos/yasm/yasm/issues/211/comments
1
2023-03-11T23:57:58Z
2023-12-12T18:27:10Z
https://github.com/yasm/yasm/issues/211
1,620,181,617
211
[ "yasm", "yasm" ]
I found a memory leak bug in yasm. Please confirm. Thanks! ### Test Environment Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master) ### How to trigger Compile the program with AddressSanitizer Run command $ touch u $ ./yasm -ium u ### Details ASAN report $./yasm -ium u ``` yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==973537==ERROR: LeakSanitizer: detected memory leaks Direct leak of 16 byte(s) in 1 object(s) allocated from: #0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_a_l_e/yasm+0x499c1d) #1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14 #2 0x511025 in yasm_intnum_copy /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/intnum.c:397:22 #3 0x638eb4 in group_assign_vstart_recurse /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/objfmts/bin/bin-objfmt.c:424:30 #4 0x632759 in bin_objfmt_output /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/objfmts/bin/bin-objfmt.c:1334:9 #5 0x4d07a2 in do_assemble /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:546:5 #6 0x4ccce0 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:749:12 #7 0x7f1562a88082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 Direct leak of 16 byte(s) in 1 object(s) allocated from: #0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_a_l_e/yasm+0x499c1d) #1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14 #2 0x510522 in yasm_intnum_create_uint /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/intnum.c:310:25 #3 0x636694 in bin_lma_create_group /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/objfmts/bin/bin-objfmt.c:248:22 #4 0x51d0f2 in yasm_object_sections_traverse /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/section.c:544:22 #5 0x62fb9e in bin_objfmt_output /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/objfmts/bin/bin-objfmt.c:1147:9 #6 0x4d07a2 in do_assemble /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:546:5 #7 0x4ccce0 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:749:12 #8 0x7f1562a88082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 SUMMARY: AddressSanitizer: 32 byte(s) leaked in 2 allocation(s). ```
yasm memory leak
https://api.github.com/repos/yasm/yasm/issues/210/comments
5
2023-03-01T02:27:11Z
2024-03-22T11:43:38Z
https://github.com/yasm/yasm/issues/210
1,604,119,944
210
[ "yasm", "yasm" ]
I found a heap-use-after-free in yasm. Please confirm. Thanks! Test Environment Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master) How to trigger Compile the program with AddressSanitizer Run command $ ./yasm -w -W -M $PoC Details ASAN report $./yasm -w -W -M $PoC ``` yasm: warning: unrecognized option `-W' yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==973256==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000011f0 at pc 0x0000005b191a bp 0x7ffe2af792f0 sp 0x7ffe2af792e8 READ of size 4 at 0x60e0000011f0 thread T0 #0 0x5b1919 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5104:45 #1 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16 #2 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23 #3 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16 #4 0x7f074a43c082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 #5 0x41d46d in _start (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x41d46d) 0x60e0000011f0 is located 48 bytes inside of 160-byte region [0x60e0000011c0,0x60e000001260) freed by thread T0 here: #0 0x4999b2 in free (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x4999b2) #1 0x53d597 in def_xfree /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:113:5 #2 0x5b381a in free_mmacro /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:1163:5 #3 0x5b05e3 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5002:25 #4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16 #5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23 #6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16 #7 0x7f074a43c082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 previously allocated by thread T0 here: #0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x499c1d) #1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14 #2 0x5c5744 in do_directive /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:3204:24 #3 0x5b13c1 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5075:13 #4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16 #5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23 #6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16 #7 0x7f074a43c082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 SUMMARY: AddressSanitizer: heap-use-after-free /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5104:45 in pp_getline Shadow bytes around the buggy address: 0x0c1c7fff81e0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff81f0: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 0x0c1c7fff8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c1c7fff8230: fa fa fa fa fa fa fa fa fd fd fd fd fd fd[fd]fd 0x0c1c7fff8240: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa 0x0c1c7fff8250: fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd 0x0c1c7fff8260: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa 0x0c1c7fff8270: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c1c7fff8280: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 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 ==973256==ABORTING ``` The URL of PoC is [PoC](https://github.com/randomssr/PoCs/blob/main/yasm/170-UAF)
yasm heap use-after-free bug
https://api.github.com/repos/yasm/yasm/issues/209/comments
1
2023-03-01T02:17:35Z
2023-05-10T05:20:07Z
https://github.com/yasm/yasm/issues/209
1,604,108,494
209
[ "yasm", "yasm" ]
I found a heap-use-after-free in yasm. Please confirm. Thanks! Test Environment Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master) How to trigger Compile the program with AddressSanitizer Run command $ ./yasm -w -W -M $PoC Details ASAN report $./yasm -w -W -M $PoC ``` yasm: warning: unrecognized option `-W' yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==973143==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000011c8 at pc 0x0000005b2d1b bp 0x7ffdc3713530 sp 0x7ffdc3713528 READ of size 8 at 0x60e0000011c8 thread T0 #0 0x5b2d1a in error /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:4823:43 #1 0x5b0c6b in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5042:21 #2 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16 #3 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23 #4 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16 #5 0x7fae91912082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 #6 0x41d46d in _start (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x41d46d) 0x60e0000011c8 is located 8 bytes inside of 160-byte region [0x60e0000011c0,0x60e000001260) freed by thread T0 here: #0 0x4999b2 in free (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x4999b2) #1 0x53d597 in def_xfree /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:113:5 #2 0x5b381a in free_mmacro /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:1163:5 #3 0x5b05e3 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5002:25 #4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16 #5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23 #6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16 #7 0x7fae91912082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 previously allocated by thread T0 here: #0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x499c1d) #1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14 #2 0x5c5744 in do_directive /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:3204:24 #3 0x5b13c1 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5075:13 #4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16 #5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23 #6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16 #7 0x7fae91912082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 SUMMARY: AddressSanitizer: heap-use-after-free /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:4823:43 in error Shadow bytes around the buggy address: 0x0c1c7fff81e0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff81f0: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 0x0c1c7fff8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c1c7fff8230: fa fa fa fa fa fa fa fa fd[fd]fd fd fd fd fd fd 0x0c1c7fff8240: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa 0x0c1c7fff8250: fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd 0x0c1c7fff8260: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa 0x0c1c7fff8270: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8280: 00 00 00 00 fa fa fa fa fa fa fa fa fa fa fa 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 ==973143==ABORTING ``` The URL of PoC is [PoC](https://github.com/randomssr/PoCs/blob/main/yasm/173-UAF)
yasm heap use-after-free bug
https://api.github.com/repos/yasm/yasm/issues/208/comments
1
2023-03-01T02:08:44Z
2023-05-10T05:20:11Z
https://github.com/yasm/yasm/issues/208
1,604,101,306
208
[ "yasm", "yasm" ]
I found a heap-use-after-free in yasm. Please confirm. Thanks! Test Environment Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master) How to trigger Compile the program with AddressSanitizer Run command $ ./yasm -w -W -M $PoC Details ASAN report $./yasm -w -W -M $PoC ``` yasm: warning: unrecognized option `-W' yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==973036==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000011c8 at pc 0x0000005b6499 bp 0x7ffc2b8cc4f0 sp 0x7ffc2b8cc4e8 READ of size 8 at 0x60e0000011c8 thread T0 #0 0x5b6498 in expand_mmac_params /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:3871:33 #1 0x5b13b4 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5070:21 #2 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16 #3 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23 #4 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16 #5 0x7fd75a0e2082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 #6 0x41d46d in _start (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x41d46d) 0x60e0000011c8 is located 8 bytes inside of 160-byte region [0x60e0000011c0,0x60e000001260) freed by thread T0 here: #0 0x4999b2 in free (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x4999b2) #1 0x53d597 in def_xfree /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:113:5 #2 0x5b381a in free_mmacro /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:1163:5 #3 0x5b05e3 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5002:25 #4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16 #5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23 #6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16 #7 0x7fd75a0e2082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 previously allocated by thread T0 here: #0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_w_W_M/yasm+0x499c1d) #1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14 #2 0x5c5744 in do_directive /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:3204:24 #3 0x5b13c1 in pp_getline /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:5075:13 #4 0x5a7c61 in nasm_preproc_get_included_file /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-preproc.c:263:16 #5 0x4ce053 in do_preproc_only /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:310:23 #6 0x4cca12 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:724:16 #7 0x7fd75a0e2082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 SUMMARY: AddressSanitizer: heap-use-after-free /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/preprocs/nasm/nasm-pp.c:3871:33 in expand_mmac_params Shadow bytes around the buggy address: 0x0c1c7fff81e0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff81f0: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 0x0c1c7fff8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8210: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff8220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0c1c7fff8230: fa fa fa fa fa fa fa fa fd[fd]fd fd fd fd fd fd 0x0c1c7fff8240: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa 0x0c1c7fff8250: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff8260: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa 0x0c1c7fff8270: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c1c7fff8280: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 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 ==973036==ABORTING ``` The URL of PoC is [PoC](https://github.com/randomssr/PoCs/blob/main/yasm/132-UAF)
yasm heap use-after-free bug
https://api.github.com/repos/yasm/yasm/issues/207/comments
1
2023-03-01T02:03:35Z
2023-05-10T05:20:08Z
https://github.com/yasm/yasm/issues/207
1,604,096,378
207
[ "yasm", "yasm" ]
yasm heap buffer overflow I found a heap-buffer-overflow in yasm. Please confirm. Thanks! Test Environment Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master) How to trigger Compile the program with AddressSanitizer Run command $ ./yasm -s -o abc --force-strict $PoC Details ASAN report $./yasm -s -o abc --force-strict $PoC ``` yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==972503==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000006fd3 at pc 0x000000717cbd bp 0x7ffe3f1cd1c0 sp 0x7ffe3f1cd1b8 READ of size 1 at 0x602000006fd3 thread T0 #0 0x717cbc in handle_dot_label /home/root/FuzzDateset/yasm/yasm-1.3.0/./modules/parsers/nasm/nasm-token.re:82:13 #1 0x704533 in nasm_parser_lex /home/root/FuzzDateset/yasm/yasm-1.3.0/./modules/parsers/nasm/nasm-token.re:384:17 #2 0x594fbb in demand_eol_ /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/parsers/nasm/nasm-parse.c:149:9 #3 0x591775 in nasm_parser_parse /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/parsers/nasm/nasm-parse.c:232:13 #4 0x590f3f in nasm_do_parse /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/parsers/nasm/nasm-parser.c:66:5 #5 0x5907fb in nasm_parser_do_parse /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/parsers/nasm/nasm-parser.c:83:5 #6 0x4d035f in do_assemble /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:519:5 #7 0x4ccce0 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:749:12 #8 0x7f675d943082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 #9 0x41d46d in _start (/home/root/randomFuzz/yasm/yasm/yasm_s_o_f/yasm+0x41d46d) 0x602000006fd3 is located 0 bytes to the right of 3-byte region [0x602000006fd0,0x602000006fd3) allocated by thread T0 here: #0 0x499c1d in __interceptor_malloc (/home/root/randomFuzz/yasm/yasm/yasm_s_o_f/yasm+0x499c1d) #1 0x53d0af in def_xmalloc /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xmalloc.c:69:14 #2 0x53d86e in yasm__xstrndup /home/root/FuzzDateset/yasm/yasm-1.3.0/libyasm/xstrdup.c:64:16 #3 0x717bfb in handle_dot_label /home/root/FuzzDateset/yasm/yasm-1.3.0/./modules/parsers/nasm/nasm-token.re:79:26 #4 0x704533 in nasm_parser_lex /home/root/FuzzDateset/yasm/yasm-1.3.0/./modules/parsers/nasm/nasm-token.re:384:17 #5 0x594fbb in demand_eol_ /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/parsers/nasm/nasm-parse.c:149:9 #6 0x591775 in nasm_parser_parse /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/parsers/nasm/nasm-parse.c:232:13 #7 0x590f3f in nasm_do_parse /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/parsers/nasm/nasm-parser.c:66:5 #8 0x5907fb in nasm_parser_do_parse /home/root/FuzzDateset/yasm/yasm-1.3.0/modules/parsers/nasm/nasm-parser.c:83:5 #9 0x4d035f in do_assemble /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:519:5 #10 0x4ccce0 in main /home/root/FuzzDateset/yasm/yasm-1.3.0/frontends/yasm/yasm.c:749:12 #11 0x7f675d943082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 SUMMARY: AddressSanitizer: heap-buffer-overflow /home/root/FuzzDateset/yasm/yasm-1.3.0/./modules/parsers/nasm/nasm-token.re:82:13 in handle_dot_label Shadow bytes around the buggy address: 0x0c047fff8da0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa 0x0c047fff8db0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa 0x0c047fff8dc0: fa fa fd fa fa fa fd fa fa fa fd fd fa fa fd fd 0x0c047fff8dd0: fa fa fd fa fa fa fd fa fa fa 05 fa fa fa 05 fa 0x0c047fff8de0: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa =>0x0c047fff8df0: fa fa fd fa fa fa fd fa fa fa[03]fa fa fa fa fa 0x0c047fff8e00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8e10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8e20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8e30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8e40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 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 ==972503==ABORTING ``` The URL of PoC is [PoC](https://github.com/randomssr/PoCs/blob/main/yasm/137-HOF)
yasm heap buffer overflow
https://api.github.com/repos/yasm/yasm/issues/206/comments
1
2023-03-01T01:50:12Z
2024-03-22T11:53:56Z
https://github.com/yasm/yasm/issues/206
1,604,082,214
206
[ "yasm", "yasm" ]
how to fix below error occurring with yasm 1.3 ? configure: error: Standard (ANSI/ISO C89) header files are required. Error doesn't occur with yasm 1.2
autogen.sh error
https://api.github.com/repos/yasm/yasm/issues/205/comments
0
2023-02-07T04:08:51Z
2023-02-07T04:08:51Z
https://github.com/yasm/yasm/issues/205
1,573,650,108
205
[ "yasm", "yasm" ]
According to the NASM docs https://www.nasm.us/xdoc/2.15.05/html/nasmdoc3.html#section-3.4.2 > Strings enclosed in backquotes support C-style \–escapes for special characters. This does not appear to be the case with yasm: ```nasm ; hello.asm global _start section .text _start: mov rax, 1 mov rdi, 1 mov rsi, message mov rdx, messageLen syscall mov rax, 60 xor rdi, rdi syscall section .data message db `Hello, World!\n` messageLen equ $-message ``` `nasm -f elf64 hello.asm && ld hello.o && ./a.out` runs successfuly and prints `Hello, World!` (with a newline at the end) `yasm -f elf64 hello.asm && ld hello.o && ./a.out` fails with the following log: ``` hello.asm:16: warning: ignoring unrecognized character ``' hello.asm:16: warning: ignoring unrecognized character `!' hello.asm:16: warning: ignoring unrecognized character `\' hello.asm:16: error: expected `,' hello.asm:16: warning: ignoring unrecognized character ``' hello.asm:16: error: undefined symbol `Hello' (first use) hello.asm:16: error: undefined symbol `World' (first use) hello.asm:16: error: (Each undefined symbol is reported only once.) ``` Version information: ``` $ nasm --version NASM version 2.15.05 compiled on Sep 24 2020 $ yasm --version yasm 1.3.0 Compiled on Apr 24 2022. Copyright (c) 2001-2014 Peter Johnson and other Yasm developers. Run yasm --license for licensing overview and summary. ``` Is there an extra flag that i need to pass for this feature to work, or is it just not supported in yasm? if the latter, i'd like to see the support for it added.
Support for backquote strings?
https://api.github.com/repos/yasm/yasm/issues/203/comments
0
2022-12-04T19:53:13Z
2022-12-04T19:55:53Z
https://github.com/yasm/yasm/issues/203
1,475,129,302
203
[ "yasm", "yasm" ]
Add `TRASHIT()` macro to set pointer to NULL in `libyasm/compat-queue.h`. This is just a hardening measure to make sure stale pointers are not left in next/prev struct members. Also fixed here: [Bug 247685](https://bugs.webkit.org/show_bug.cgi?id=247685): Add TRASHIT() macro to set pointer to NULL in yasm/libyasm/compat-queue.h https://github.com/WebKit/WebKit/commit/90805ce353ec1226d339911cb524dad9e819e3e8
Add TRASHIT() macro to set pointer to NULL in libyasm/compat-queue.h
https://api.github.com/repos/yasm/yasm/issues/202/comments
0
2022-11-12T03:56:28Z
2022-11-12T03:56:28Z
https://github.com/yasm/yasm/issues/202
1,446,227,227
202
[ "yasm", "yasm" ]
Trying build [libdav1d](https://code.videolan.org/videolan/dav1d) asm source for arm Here's command i use "yasm -f elf64 -p gas dav1d/src and then I catch an error <img width="543" alt="SegfaultMacos" src="https://user-images.githubusercontent.com/45670849/187673129-56ead6fe-784b-41bb-80c7-cd7089e6ee80.png"> Where is the error?
segmentation fault on MacOS Monterey 12.2
https://api.github.com/repos/yasm/yasm/issues/199/comments
2
2022-08-31T11:54:42Z
2023-07-15T13:54:13Z
https://github.com/yasm/yasm/issues/199
1,357,227,323
199
[ "yasm", "yasm" ]
how to fix the error on ubuntu 22.04 ? thanks checking for sys/stat.h... (cached) yes configure: error: Standard (ANSI/ISO C89) header files are required. works on ubuntu 18.04
autogen.sh error on ubuntu 22.04
https://api.github.com/repos/yasm/yasm/issues/197/comments
0
2022-07-21T20:07:40Z
2022-07-21T20:07:40Z
https://github.com/yasm/yasm/issues/197
1,313,745,509
197
[ "yasm", "yasm" ]
Hi, When i used -f dosexe option, I found that yasm crashed. <img width="437" alt="image" src="https://user-images.githubusercontent.com/39018042/172167231-dcb55bf1-3068-4697-ae50-15205868dac0.png"> Here is the command : ```./yasm -f dosexe ./poc``` My poc : https://gist.githubusercontent.com/naihsin/cc5318fd1f0655e60288eabeff6da930/raw/892829b7351a45eca138c30a071fc5d3736e5c2e/poc The yasm version is 1.3.0.54.gffbd2 <img width="610" alt="截圖 2022-06-06 下午8 52 20" src="https://user-images.githubusercontent.com/39018042/172166144-db73dc6c-93a1-41f7-ab7f-ec02bab2123e.png"> I compiled the yasm code by these option ``` ./autogen.sh; make distclean CFLAGS="-g -m32" CXXFLAGS="-g -m32" ./configure --prefix=`pwd` make clean; make ``` Here shows an overflow bug via valgrind tool ``` ==29325== Command: ./yasm -f dosexe ./poc ==29325== ==29325== Conditional jump or move depends on uninitialised value(s) ==29325== at 0x409F561: vfprintf (vfprintf.c:1632) ==29325== by 0x40C23EE: vsnprintf (vsnprintf.c:114) ==29325== by 0x8053C8B: yasm_error_set_va (errwarn.c:279) ==29325== by 0x8053CC2: yasm_error_set (errwarn.c:290) ==29325== by 0x808EADB: dosexe_objfmt_output (bin-objfmt.c:1928) ==29325== by 0x8049C79: do_assemble (yasm.c:548) ==29325== by 0x804A3AB: main (yasm.c:753) ==29325== ==29325== Use of uninitialised value of size 4 ==29325== at 0x40A0393: vfprintf (vfprintf.c:1632) ==29325== by 0x40C23EE: vsnprintf (vsnprintf.c:114) ==29325== by 0x8053C8B: yasm_error_set_va (errwarn.c:279) ==29325== by 0x8053CC2: yasm_error_set (errwarn.c:290) ==29325== by 0x808EADB: dosexe_objfmt_output (bin-objfmt.c:1928) ==29325== by 0x8049C79: do_assemble (yasm.c:548) ==29325== by 0x804A3AB: main (yasm.c:753) ==29325== ==29325== Invalid read of size 1 ==29325== at 0x40A0393: vfprintf (vfprintf.c:1632) ==29325== by 0x40C23EE: vsnprintf (vsnprintf.c:114) ==29325== by 0x8053C8B: yasm_error_set_va (errwarn.c:279) ==29325== by 0x8053CC2: yasm_error_set (errwarn.c:290) ==29325== by 0x808EADB: dosexe_objfmt_output (bin-objfmt.c:1928) ==29325== by 0x8049C79: do_assemble (yasm.c:548) ==29325== by 0x804A3AB: main (yasm.c:753) ==29325== Address 0x1 is not stack'd, malloc'd or (recently) free'd ```
Maybe there is a buffer overflow bug in yasm_error_set_va() libyasm/errwarn.c
https://api.github.com/repos/yasm/yasm/issues/196/comments
0
2022-06-06T13:12:09Z
2022-06-06T13:12:09Z
https://github.com/yasm/yasm/issues/196
1,261,829,266
196
[ "yasm", "yasm" ]
error description: when the argument is set to " -o . " (there are other effective conditions to crash when using with VS2022l) the function "yasm__createpath(objdir_pathname)" returns 0xffffffff which is -1 as index, objdir_pathname[i] = '/'; objdir_pathname[i + 1] = '\0'; will write the byte before objdir_pathname[0] and therefore cause crash while freeing this range of memory. my solution: if (((int)i) < 0) { objdir_pathname[0] = '\0'; } else { objdir_pathname[i] = '/'; objdir_pathname[i + 1] = '\0'; } Best Regards, Yilin
Memory error in vsyasm resulting in crash
https://api.github.com/repos/yasm/yasm/issues/195/comments
1
2022-05-27T04:33:02Z
2022-06-02T03:57:56Z
https://github.com/yasm/yasm/issues/195
1,250,323,068
195
[ "yasm", "yasm" ]
**Description:** An invalid memory address dereference was discovered at modules/preprocs/nasm/nasm-pp.c:3494. The vulnerability causes a segmentation fault and application crash. **Version:** ``` ./yasm --version yasm 1.3.0.52.g4176 Compiled on Dec 16 2021. Copyright (c) 2001-2014 Peter Johnson and other Yasm developers. Run yasm --license for licensing overview and summary. ``` **System information** Ubuntu 20.04 focal, AMD EPYC 7742 64-Core @ 16x 2.25GHz **command:** ``` ./yasm ./poc ``` [poc.zip](https://github.com/yasm/yasm/files/7728237/poc.zip) **Result** ``` ./yasm ./poc [1] 236948 segmentation fault ./test/yasm ./poc ``` **gdb** ``` Program received signal SIGSEGV, Segmentation fault. 0x00005555555c93cf in do_directive (tline=0x7ffff7da1c30) at modules/preprocs/nasm/nasm-pp.c:3494 3494 if (t->type != TOK_STRING) LEGEND: STACK | HEAP | CODE | DATA | RWX | RODATA ────────────────────────────────────────────[ REGISTERS ]───────────────────────────────────────────── RAX 0x0 RBX 0x555555611c30 (__libc_csu_init) ◂— endbr64 RCX 0x0 RDX 0x7ffff7da1bf0 —▸ 0x7ffff7da1bd0 —▸ 0x7ffff7da1bb0 —▸ 0x7ffff7da1b90 —▸ 0x7ffff7da1b70 ◂— ... RDI 0x0 RSI 0x7ffff7da1c10 —▸ 0x7ffff7da1bf0 —▸ 0x7ffff7da1bd0 —▸ 0x7ffff7da1bb0 —▸ 0x7ffff7da1b90 ◂— ... R8 0x0 R9 0x3 R10 0x7ffff7f48210 (__strcasecmp_l_avx+4556) ◂— vpslldq xmm2, xmm2, 3 R11 0x7ffff7f5e3c0 (_nl_C_LC_CTYPE_class+256) ◂— 0x2000200020002 R12 0x55555558e7f0 (_start) ◂— endbr64 R13 0x7fffffffe260 ◂— 0x2 R14 0x0 R15 0x0 RBP 0x7fffffffddb0 —▸ 0x7fffffffde30 —▸ 0x7fffffffde90 —▸ 0x7fffffffdf00 —▸ 0x7fffffffe010 ◂— ... RSP 0x7fffffffdb70 —▸ 0x555555673710 ◂— "%macro strlen_test 1\n %strlen len %2 ; not existing argument\n%endmacro\n\nstrlen_test 'a'\n" RIP 0x5555555c93cf (do_directive+13816) ◂— mov eax, dword ptr [rax + 0x18] ──────────────────────────────────────────────[ DISASM ]────────────────────────────────────────────── ► 0x5555555c93cf <do_directive+13816> mov eax, dword ptr [rax + 0x18] 0x5555555c93d2 <do_directive+13819> cmp eax, 5 0x5555555c93d5 <do_directive+13822> je do_directive+13886 <do_directive+13886> ↓ 0x5555555c9415 <do_directive+13886> mov rax, qword ptr [rip + 0x8b714] <0x555555654b30> 0x5555555c941c <do_directive+13893> mov edi, 0x20 0x5555555c9421 <do_directive+13898> call rax 0x5555555c9423 <do_directive+13900> mov qword ptr [rbp - 0x1d0], rax 0x5555555c942a <do_directive+13907> mov rax, qword ptr [rbp - 0x1d0] 0x5555555c9431 <do_directive+13914> mov qword ptr [rax], 0 0x5555555c9438 <do_directive+13921> mov rax, qword ptr [rbp - 0x200] 0x5555555c943f <do_directive+13928> mov rax, qword ptr [rax + 8] ──────────────────────────────────────────[ SOURCE (CODE) ]─────────────────────────────────────────── In file: /root/fuzzing/yasm/yasm/modules/preprocs/nasm/nasm-pp.c 3489 3490 t = tline; 3491 while (tok_type_(t, TOK_WHITESPACE)) 3492 t = t->next; 3493 /* t should now point to the string */ ► 3494 if (t->type != TOK_STRING) 3495 { 3496 error(ERR_NONFATAL, 3497 "`%%strlen` requires string as second parameter"); 3498 free_tlist(tline); 3499 free_tlist(origline); ──────────────────────────────────────────────[ STACK ]─────────────────────────────────────────────── 00:0000│ rsp 0x7fffffffdb70 —▸ 0x555555673710 ◂— "%macro strlen_test 1\n %strlen len %2 ; not existing argument\n%endmacro\n\nstrlen_test 'a'\n" 01:0008│ 0x7fffffffdb78 —▸ 0x7ffff7da1c30 ◂— 0x0 02:0010│ 0x7fffffffdb80 ◂— 0xfffffffe5566eed0 03:0018│ 0x7fffffffdb88 ◂— 0x3d0000003d /* '=' */ 04:0020│ 0x7fffffffdb90 ◂— 0x555500000000 05:0028│ 0x7fffffffdb98 —▸ 0x7ffff7e43e9d (_IO_file_doallocate+173) ◂— mov eax, 1 06:0030│ 0x7fffffffdba0 ◂— 0x80 07:0038│ 0x7fffffffdba8 ◂— 9 /* '\t' */ ────────────────────────────────────────────[ BACKTRACE ]───────────────────────────────────────────── ► f 0 0x5555555c93cf do_directive+13816 f 1 0x5555555cd03f pp_getline+1409 f 2 0x5555555c019a nasm_preproc_get_line+95 f 3 0x5555555bab9f nasm_parser_parse+813 f 4 0x5555555ba1f5 nasm_do_parse+273 f 5 0x5555555ba28d nasm_parser_do_parse+67 f 6 0x55555558f4b5 do_assemble+1950 f 7 0x55555558fdd0 main+1605 ────────────────────────────────────────────────────────────────────────────────────────────────────── pwndbg> bt #0 0x00005555555c93cf in do_directive (tline=0x7ffff7da1c30) at modules/preprocs/nasm/nasm-pp.c:3494 #1 0x00005555555cd03f in pp_getline () at modules/preprocs/nasm/nasm-pp.c:5083 #2 0x00005555555c019a in nasm_preproc_get_line (preproc=0x55555566b530) at modules/preprocs/nasm/nasm-preproc.c:198 #3 0x00005555555bab9f in nasm_parser_parse (parser_nasm=0x7fffffffdf40) at modules/parsers/nasm/nasm-parse.c:219 #4 0x00005555555ba1f5 in nasm_do_parse (object=0x55555566a160, pp=0x55555566b530, save_input=0, linemap=0x555555669c90, errwarns=0x555555669c70, tasm=0) at modules/parsers/nasm/nasm-parser.c:66 #5 0x00005555555ba28d in nasm_parser_do_parse (object=0x55555566a160, pp=0x55555566b530, save_input=0, linemap=0x555555669c90, errwarns=0x555555669c70) at modules/parsers/nasm/nasm-parser.c:83 #6 0x000055555558f4b5 in do_assemble () at frontends/yasm/yasm.c:521 #7 0x000055555558fdd0 in main (argc=2, argv=0x7fffffffe268) at frontends/yasm/yasm.c:753 #8 0x00007ffff7de60b3 in __libc_start_main (main=0x55555558f78b <main>, argc=2, argv=0x7fffffffe268, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe258) at ../csu/libc-start.c:308 #9 0x000055555558e81e in _start () ```
An invalid memory address dereference at modules/preprocs/nasm/nasm-pp.c:3494
https://api.github.com/repos/yasm/yasm/issues/194/comments
0
2021-12-16T14:48:18Z
2021-12-16T14:48:18Z
https://github.com/yasm/yasm/issues/194
1,082,283,708
194
[ "yasm", "yasm" ]
enviroment:win10 vs2019(MSVC140, 141) ![error](https://user-images.githubusercontent.com/40573733/142796468-2213aef9-57db-49a8-905c-f0bff5fb29a2.png)
yasm-tool[core] is only supported on 'native & !uwp'
https://api.github.com/repos/yasm/yasm/issues/193/comments
3
2021-11-22T03:25:24Z
2022-02-11T12:14:29Z
https://github.com/yasm/yasm/issues/193
1,059,629,490
193
[ "yasm", "yasm" ]
On this page: https://en.wikipedia.org/wiki/Comparison_of_assemblers#x86-64_assemblers Yasm is listed as "not in active development". This stopped me considering it until I went to github and saw that development is continuing. But I didn't want to change that status myself in case you're just maintaining?
Wikipedia says Yasm is not in active development
https://api.github.com/repos/yasm/yasm/issues/191/comments
0
2021-11-12T10:10:14Z
2021-11-12T10:10:14Z
https://github.com/yasm/yasm/issues/191
1,051,794,786
191
[ "yasm", "yasm" ]
Hi there, I was unable to download a release due to an expired certificate http://www.tortall.net/projects/yasm/releases/yasm-1.3.0.tar.gz ![Screenshot from 2021-11-10 23-32-16](https://user-images.githubusercontent.com/5497998/141113881-253d154b-9588-4565-9084-9e7e2755f2d7.png) @PeterJohnson
Cert Expired www.tortall.net
https://api.github.com/repos/yasm/yasm/issues/190/comments
4
2021-11-10T12:36:41Z
2021-11-11T02:28:03Z
https://github.com/yasm/yasm/issues/190
1,049,771,004
190
[ "yasm", "yasm" ]
It seems that immediate operands using characters are unsupported. ``` $ cat >| fuck.s .globl main main: movb $'\n', %eax ret $ as -fatal-warnings -o /dev/null fuck.s $ yasm -Werror -felf64 -pgas -o /dev/null fuck.s : error: warnings being treated as errors fuck.s:3: error: unexpected end of file in string $ sed -i "s/'\\\\n'/10/" fuck.s $ yasm -Werror -felf64 -pgas -o /dev/null fuck.s : error: warnings being treated as errors $ ``` Is that due to the following code, or will I need to fiddle around with `parse_expr()`, `parse_operand()` and friends? Probably both, right? https://github.com/yasm/yasm/blob/41762bead150fdae59687b35c8acd1c4ae0f1575/modules/parsers/gas/gas-token.re#L510-L514
Character immediates appear to be unsupported when using the GNU parser?
https://api.github.com/repos/yasm/yasm/issues/188/comments
1
2021-11-01T13:23:34Z
2021-11-01T13:27:37Z
https://github.com/yasm/yasm/issues/188
1,041,170,559
188
[ "yasm", "yasm" ]
yasm.s:9: error: expression missing after `$' yasm.s:22: error: directive `.global' requires an argument yasm.s:23: error: label or instruction expected at start of line s to o .global xxxxf xxxxf: pushq %rbp movq %rsp, %rbp subq $16, %rsp .LB1: #instruction start "1 <- temporary": #instruction start "1 = constant": movabsq $a, %rdi leaq -4(%rbp), %rsi movl 0(%rdi), %eax movl %eax, 0(%rsi) #instruction start "clear stack bucket 1": # EXIT IS OF TYPE : 1 movq -4(%rbp), %rax leave ret .LB2: # EXIT IS OF TYPE : 0 ud2 .section .data .global a a: .zero 4 .section .text
bug? $
https://api.github.com/repos/yasm/yasm/issues/187/comments
4
2021-10-28T22:30:05Z
2022-05-26T07:16:25Z
https://github.com/yasm/yasm/issues/187
1,039,004,648
187
[ "yasm", "yasm" ]
Here is a small example of how I can reliably trigger it: ```c #include <libyasm/bitvect.h> #include <stdlib.h> int main() { wordptr v = BitVector_Create(64, 1); BitVector_Destroy(v); void* p = malloc(1024); free(p); return 0; } ``` Running it gives me: ``` small.o: malloc.c:2539: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed. Aborted (core dumped) ``` I'm using: `gcc (SUSE Linux) 11.1.1 20210721 [revision 076930b9690ac3564638636f6b13bbb6bc608aea]` and `GNU C Library (GNU libc) release release version 2.33 (git 9826b03b74)`. I compiled libyasm myself with the same tools. Upon exploring the sources I found out that when you create a bitvector with bitsize 64, it calculates the wrong word and byte sizes of 64 and 167 for it, and when you try to fill the vector, it overwrites heap structures causing heap corruption.
Heap corruption in BitVector_Create (and other bitvector functions)
https://api.github.com/repos/yasm/yasm/issues/185/comments
1
2021-08-19T12:34:22Z
2021-08-19T12:43:43Z
https://github.com/yasm/yasm/issues/185
974,616,114
185
[ "yasm", "yasm" ]
This seems to have occurred again as of 8 days ago: https://github.com/yasm/yasm/issues/106 I was trying to install the ffmpeg:x86-windows package via vcpkg on my Windows machine, which depends on yasm and currently points to https://www.tortall.net/projects/yasm/snapshots/v1.3.0.6.g1962/yasm-1.3.0.6.g1962.exe https://github.com/microsoft/vcpkg/blob/8886d85ad0215a7f30459f5a3c495a0f7c4d6a88/scripts/cmake/vcpkg_find_acquire_program.cmake#L91 ``` [DEBUG] Downloading https://www.tortall.net/projects/yasm/snapshots/v1.3.0.6.g1962/yasm-1.3.0.6.g1962.exe Failed to download from mirror set: https://www.tortall.net/projects/yasm/snapshots/v1.3.0.6.g1962/yasm-1.3.0.6.g1962.exe: WinHttpSendRequest() failed: 12175 ```
Certificate for https://www.tortall.net has expired, again
https://api.github.com/repos/yasm/yasm/issues/182/comments
7
2021-07-27T19:22:25Z
2021-08-11T16:22:20Z
https://github.com/yasm/yasm/issues/182
954,195,887
182
[ "yasm", "yasm" ]
Regarding `UWOP_SET_FPREG`, according to https://docs.microsoft.com/en-us/cpp/build/exception-handling-x64?view=msvc-160: > The operation info field is reserved and shouldn't be used. But yasm appears to set it to the frame pointer register: https://github.com/yasm/yasm/blob/41762bead150fdae59687b35c8acd1c4ae0f1575/modules/objfmts/coff/coff-objfmt.c#L2078 It's an open question whether this is actually a problem! - I just noticed this while checking my own unwind data against yasm's output.
Win64 unwind data - UWOP_SET_FPREG reserved info field is set
https://api.github.com/repos/yasm/yasm/issues/181/comments
1
2021-07-20T00:50:30Z
2021-11-01T13:41:41Z
https://github.com/yasm/yasm/issues/181
948,142,441
181
[ "yasm", "yasm" ]
Using this test file to run the GAS-style preprocessor, yasm crashes: ``` .set counter, 0 .macro REPEATER_2 count=5 .rept \count .set counter, counter+1 .endr .endm REPEATER_2 ``` Command line: ```bash yasm -r gas -e yasm_crash.S -o yasm_crash.i ``` Output: ``` free(): invalid pointer ``` Backtrace: ``` #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007ffff75e8921 in __GI_abort () at abort.c:79 #2 0x00007ffff7631967 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff775eb0d "%s\n") at ../sysdeps/posix/libc_fatal.c:181 #3 0x00007ffff76389da in malloc_printerr (str=str@entry=0x7ffff775cd08 "free(): invalid pointer") at malloc.c:5342 #4 0x00007ffff763ff0c in _int_free (have_lock=0, p=0x55555560eca4, av=0x7ffff7993c40 <main_arena>) at malloc.c:4167 #5 __GI___libc_free (mem=0x55555560ecb4) at malloc.c:3134 #6 0x00007ffff7bc904a in def_xfree (p=0x55555560ecb4) at ./yasm/libyasm/xmalloc.c:113 #7 0x00007ffff7334c90 in eval_rept (pp=0x55555560cac0, unused=0, arg1=0x55555560ec76 "5") at ./yasm/modules/preprocs/gas/gas-preproc.c:1002 #8 0x00007ffff733563d in process_line (pp=0x55555560cac0, line_ptr=0x7fffffffd608) at ./yasm/modules/preprocs/gas/gas-preproc.c:1203 #9 0x00007ffff7335d63 in gas_preproc_get_line (preproc=0x55555560cac0) at ./yasm/modules/preprocs/gas/gas-preproc.c:1336 #10 0x0000555555403261 in do_preproc_only () at ./yasm/frontends/yasm/yasm.c:325 #11 0x000055555540417f in main (argc=7, argv=0x7fffffffd798) at ./yasm/frontends/yasm/yasm.c:728 ```
GAS: set inside repm crashes
https://api.github.com/repos/yasm/yasm/issues/176/comments
9
2021-05-19T13:44:00Z
2023-05-13T04:13:45Z
https://github.com/yasm/yasm/issues/176
895,464,774
176
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-1114-hash-null-pointer-deref ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ASAN:SIGSEGV ================================================================= ==11392==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7f3f936ac15c bp 0x7ffc98fb57a0 sp 0x7ffc98fb5760 T0) #0 0x7f3f936ac15b in hash test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:1114 #1 0x7f3f936b5ab9 in do_directive test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:3103 #2 0x7f3f936c0333 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5083 #3 0x7f3f936a9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #4 0x7f3f9369b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #5 0x7f3f9368f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #6 0x7f3f9368f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #7 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #8 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #9 0x7f3f967b582f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #10 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:1114 hash ==11392==ABORTING ```
A NULL pointer dereference in the function hash() modules/preprocs/nasm/nasm-pp.c:1114
https://api.github.com/repos/yasm/yasm/issues/175/comments
1
2021-05-19T08:30:54Z
2024-03-21T11:46:29Z
https://github.com/yasm/yasm/issues/175
895,151,364
175
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-1113-yasm_expr__copy_except-null-pointer-deref ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ASAN:SIGSEGV ================================================================= ==10834==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000010 (pc 0x7fdb4c7eafb3 bp 0x7fff7a57d890 sp 0x7fff7a57d840 T0) #0 0x7fdb4c7eafb2 in yasm_expr__copy_except test/yasm-uaf/SRC_asan/libyasm/expr.c:999 #1 0x7fdb4908fad6 in nasm_parser_directive test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:1584 #2 0x7fdb4909bd3c in parse_line test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:377 #3 0x7fdb4909bd3c in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:231 #4 0x7fdb4908f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #5 0x7fdb4908f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #6 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #7 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #8 0x7fdb4c21382f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #9 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV test/yasm-uaf/SRC_asan/libyasm/expr.c:999 yasm_expr__copy_except ==10834==ABORTING ```
A NULL pointer dereference in the function yasm_expr__copy_except() libyasm/expr.c:999
https://api.github.com/repos/yasm/yasm/issues/174/comments
2
2021-05-19T08:30:07Z
2024-03-22T14:00:39Z
https://github.com/yasm/yasm/issues/174
895,150,639
174
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-4760-expand_mmacro-null-pointer-deref ASAN info: ```C ASAN:SIGSEGV ================================================================= ==17359==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000001 (pc 0x7f2e6f6c3fc6 bp 0x7ffd238e70b0 sp 0x7ffd238e6f00 T0) #0 0x7f2e6f6c3fc5 in expand_mmacro test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:4764 #1 0x7f2e6f6c3fc5 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5128 #2 0x7f2e6f6a9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #3 0x7f2e6f69b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #4 0x7f2e6f68f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #5 0x7f2e6f68f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #6 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #7 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #8 0x7f2e7286b82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #9 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:4764 expand_mmacro ==17359==ABORTING ```
A NULL pointer dereference in the function expand_mmacro() modules/preprocs/nasm/nasm-pp.c:4764
https://api.github.com/repos/yasm/yasm/issues/173/comments
1
2021-05-19T08:29:17Z
2024-03-21T12:35:36Z
https://github.com/yasm/yasm/issues/173
895,149,848
173
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) I think it is probably a similar issue as [#142](https://github.com/yasm/yasm/issues/142) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-4352-expand_smacro-null-pointer-deref ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ASAN:SIGSEGV ================================================================= ==16729==ERROR: AddressSanitizer: SEGV on unknown address 0x00000000001c (pc 0x7fa8f23b196d bp 0x7fff0c7cf990 sp 0x7fff0c7cf820 T0) #0 0x7fa8f23b196c in expand_smacro test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:4229 #1 0x7fa8f23c0ac7 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5127 #2 0x7fa8f23a9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #3 0x7fa8f239b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #4 0x7fa8f238f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #5 0x7fa8f238f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #6 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #7 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #8 0x7fa8f559882f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #9 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:4229 expand_smacro ==16729==ABORTING ```
A NULL pointer dereference in the function expand_smacro() modules/preprocs/nasm/nasm-pp.c:4229
https://api.github.com/repos/yasm/yasm/issues/172/comments
1
2021-05-19T08:28:18Z
2024-03-21T12:36:44Z
https://github.com/yasm/yasm/issues/172
895,148,925
172
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) I think it is probably a similar issue as [#151](https://github.com/yasm/yasm/issues/151) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-3857-expand_mmac_params-null-pointer-deref ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ASAN:SIGSEGV ================================================================= ==15506==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000001 (pc 0x7fc6c3caf512 bp 0x7ffceebde200 sp 0x7ffceebde060 T0) #0 0x7fc6c3caf511 in expand_mmac_params test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:3861 #1 0x7fc6c3cc08e8 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5078 #2 0x7fc6c3ca9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #3 0x7fc6c3c9b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #4 0x7fc6c3c8f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #5 0x7fc6c3c8f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #6 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #7 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #8 0x7fc6c6db382f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #9 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:3861 expand_mmac_params ==15506==ABORTING ```
A NULL pointer dereference in the function expand_mmac_params() modules/preprocs/nasm/nasm-pp.c:3861
https://api.github.com/repos/yasm/yasm/issues/171/comments
2
2021-05-19T08:27:21Z
2024-03-21T11:48:05Z
https://github.com/yasm/yasm/issues/171
895,147,985
171
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-3811-find_cc-null-pointer-deref ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ASAN:SIGSEGV ================================================================= ==14891==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000018 (pc 0x7f8500dab0e4 bp 0x7ffc37b91380 sp 0x7ffc37b91340 T0) #0 0x7f8500dab0e3 in find_cc test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:3815 #1 0x7f8500db0692 in expand_mmac_params test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:3986 #2 0x7f8500dc08e8 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5078 #3 0x7f8500da9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #4 0x7f8500d9b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #5 0x7f8500d8f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #6 0x7f8500d8f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #7 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #8 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #9 0x7f8503f0482f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #10 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:3815 find_cc ==14891==ABORTING ```
A NULL pointer dereference in the function find_cc() modules/preprocs/nasm/nasm-pp.c:3815
https://api.github.com/repos/yasm/yasm/issues/170/comments
1
2021-05-19T08:26:28Z
2024-03-21T12:44:18Z
https://github.com/yasm/yasm/issues/170
895,147,145
170
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) I think it is probably a similar issue as [#142](https://github.com/yasm/yasm/issues/142) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-2352-do_directive-null-pointer-deref ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ASAN:SIGSEGV ================================================================= ==14280==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000001 (pc 0x7f6361db4b98 bp 0x7ffe9673f060 sp 0x7ffe9673ece0 T0) #0 0x7f6361db4b97 in do_directive test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:2355 #1 0x7f6361dc0333 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5083 #2 0x7f6361da9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #3 0x7f6361d9b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #4 0x7f6361d8f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #5 0x7f6361d8f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #6 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #7 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #8 0x7f6364ee182f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #9 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:2355 do_directive ==14280==ABORTING ```
A NULL pointer dereference in the function do_directive() modules/preprocs/nasm/nasm-pp.c:2355
https://api.github.com/repos/yasm/yasm/issues/169/comments
1
2021-05-19T08:25:00Z
2024-03-21T11:40:51Z
https://github.com/yasm/yasm/issues/169
895,145,758
169
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-2134-if_condition-null-pointer-deref ASAN info: ```C ASAN:SIGSEGV ================================================================= ==13685==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7f1a02e5e870 bp 0x7fffcb38b530 sp 0x7fffcb38b380 T0) #0 0x7f1a02e5e86f in if_condition test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:2134 #1 0x7f1a02eb88c7 in do_directive test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:2907 #2 0x7f1a02ec0333 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5083 #3 0x7f1a02ea9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #4 0x7f1a02e9b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #5 0x7f1a02e8f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #6 0x7f1a02e8f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #7 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #8 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #9 0x7f1a0603682f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #10 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:2134 if_condition ==13685==ABORTING ```
A NULL pointer dereference in the function if_condition() modules/preprocs/nasm/nasm-pp.c:2134
https://api.github.com/repos/yasm/yasm/issues/168/comments
1
2021-05-19T08:24:08Z
2024-03-21T11:51:21Z
https://github.com/yasm/yasm/issues/168
895,144,888
168
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-1595-nasm_parser_directive-null-pointer-deref ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ASAN:SIGSEGV ================================================================= ==13148==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7f3a60e8fbb7 bp 0x7fff5f933810 sp 0x7fff5f933720 T0) #0 0x7f3a60e8fbb6 in nasm_parser_directive test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:1596 #1 0x7f3a60e9bd3c in parse_line test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:377 #2 0x7f3a60e9bd3c in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:231 #3 0x7f3a60e8f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #4 0x7f3a60e8f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #5 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #6 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #7 0x7f3a6405182f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #8 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:1596 nasm_parser_directive ==13148==ABORTING ```
A NULL pointer dereference in the function nasm_parser_directive() modules/parsers/nasm/nasm-parse.c:1596
https://api.github.com/repos/yasm/yasm/issues/167/comments
1
2021-05-19T08:23:17Z
2024-03-21T11:50:13Z
https://github.com/yasm/yasm/issues/167
895,144,100
167
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) I think it is probably a similar issue as [#83](https://github.com/yasm/yasm/issues/83) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-1377-yasm_expr_get_intnum-null-pointer-deref ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ASAN:SIGSEGV ================================================================= ==12603==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7f421b49db7e bp 0x7ffc83d244d0 sp 0x7ffc83d244c0 T0) #0 0x7f421b49db7d in yasm_expr_get_intnum test/yasm-uaf/SRC_asan/libyasm/expr.c:1263 #1 0x7f421b487b9e in bc_align_finalize test/yasm-uaf/SRC_asan/libyasm/bc-align.c:108 #2 0x7f421b48c6ee in yasm_bc_finalize test/yasm-uaf/SRC_asan/libyasm/bytecode.c:176 #3 0x7f421b4b9bd2 in yasm_object_finalize test/yasm-uaf/SRC_asan/libyasm/section.c:528 #4 0x402ca9 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:527 #5 0x402ca9 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #6 0x7f421aeba82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #7 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV test/yasm-uaf/SRC_asan/libyasm/expr.c:1263 yasm_expr_get_intnum ==12603==ABORTING ```
A NULL pointer dereference in the function yasm_expr_get_intnum() libyasm/expr.c:1263
https://api.github.com/repos/yasm/yasm/issues/166/comments
4
2021-05-19T08:22:19Z
2024-03-22T14:15:04Z
https://github.com/yasm/yasm/issues/166
895,143,168
166
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) I think it is probably a similar issue as [#126](https://github.com/yasm/yasm/issues/126 ) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-1226-expr_traverse_nodes_post-UAF ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==11980==ERROR: AddressSanitizer: heap-use-after-free on address 0x60600000e5b0 at pc 0x7f418ef4a94b bp 0x7ffedeadea70 sp 0x7ffedeadea60 READ of size 4 at 0x60600000e5b0 thread T0 #0 0x7f418ef4a94a in expr_traverse_nodes_post test/yasm-uaf/SRC_asan/libyasm/expr.c:1112 #1 0x7f418ef4a94a in yasm_expr_destroy test/yasm-uaf/SRC_asan/libyasm/expr.c:1045 #2 0x7f418b7ebda1 in bin_section_data_destroy test/yasm-uaf/SRC_asan/modules/objfmts/bin/bin-objfmt.c:1684 #3 0x7f418ef2e548 in yasm__assoc_data_destroy test/yasm-uaf/SRC_asan/libyasm/assocdat.c:128 #4 0x7f418ef6dd24 in yasm_section_destroy test/yasm-uaf/SRC_asan/libyasm/section.c:676 #5 0x7f418ef6dd24 in yasm_object_destroy test/yasm-uaf/SRC_asan/libyasm/section.c:470 #6 0x404ad4 in cleanup test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:799 #7 0x4053e3 in check_errors test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:778 #8 0x402c9a in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:524 #9 0x402c9a in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #10 0x7f418e96f82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #11 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) 0x60600000e5b0 is located 16 bytes inside of 56-byte region [0x60600000e5a0,0x60600000e5d8) freed by thread T0 here: #0 0x7f418f2292ca in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x982ca) #1 0x7f418ef76caa in yasm_dir_helper_expr test/yasm-uaf/SRC_asan/libyasm/valparam.c:312 #2 0x7f418ef769ff in yasm_dir_helper test/yasm-uaf/SRC_asan/libyasm/valparam.c:241 #3 0x7f418b7eb34b in bin_objfmt_section_switch test/yasm-uaf/SRC_asan/modules/objfmts/bin/bin-objfmt.c:1521 #4 0x7f418ef6cd75 in dir_section test/yasm-uaf/SRC_asan/libyasm/section.c:154 #5 0x7f418ef6d838 in yasm_object_directive test/yasm-uaf/SRC_asan/libyasm/section.c:377 #6 0x7f418b78f804 in nasm_parser_directive test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:1569 #7 0x7f418b79bd3c in parse_line test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:377 #8 0x7f418b79bd3c in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:231 #9 0x7f418b78f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #10 0x7f418b78f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #11 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #12 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #13 0x7f418e96f82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) previously allocated by thread T0 here: #0 0x7f418f229602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7f418ef7a769 in def_xmalloc test/yasm-uaf/SRC_asan/libyasm/xmalloc.c:69 #2 0x7f418ef46fd2 in yasm_expr__copy_except test/yasm-uaf/SRC_asan/libyasm/expr.c:998 #3 0x7f418ef76cd0 in yasm_dir_helper_expr test/yasm-uaf/SRC_asan/libyasm/valparam.c:313 #4 0x7f418ef769ff in yasm_dir_helper test/yasm-uaf/SRC_asan/libyasm/valparam.c:241 #5 0x7f418b7eb34b in bin_objfmt_section_switch test/yasm-uaf/SRC_asan/modules/objfmts/bin/bin-objfmt.c:1521 #6 0x7f418ef6cd75 in dir_section test/yasm-uaf/SRC_asan/libyasm/section.c:154 #7 0x7f418ef6d838 in yasm_object_directive test/yasm-uaf/SRC_asan/libyasm/section.c:377 #8 0x7f418b78f804 in nasm_parser_directive test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:1569 #9 0x7f418b79bd3c in parse_line test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:377 #10 0x7f418b79bd3c in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:231 #11 0x7f418b78f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #12 0x7f418b78f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #13 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #14 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #15 0x7f418e96f82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) SUMMARY: AddressSanitizer: heap-use-after-free test/yasm-uaf/SRC_asan/libyasm/expr.c:1112 expr_traverse_nodes_post Shadow bytes around the buggy address: 0x0c0c7fff9c60: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9c70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9c80: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9c90: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9ca0: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fa =>0x0c0c7fff9cb0: fa fa fa fa fd fd[fd]fd fd fd fd fa fa fa fa fa 0x0c0c7fff9cc0: fd fd fd fd fd fd fd fa fa fa fa fa fd fd fd fd 0x0c0c7fff9cd0: fd fd fd fa fa fa fa fa fd fd fd fd fd fd fd fa 0x0c0c7fff9ce0: fa fa fa fa fd fd fd fd fd fd fd fa fa fa fa fa 0x0c0c7fff9cf0: fd fd fd fd fd fd fd fa fa fa fa fa fd fd fd fd 0x0c0c7fff9d00: fd fd fd fa fa fa fa fa fd fd fd fd fd fd fd fd 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 Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 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 ==11980==ABORTING ```
AddressSanitizer: heap-use-after-free in expr_traverse_nodes_post() libyasm/expr.c:1112
https://api.github.com/repos/yasm/yasm/issues/165/comments
1
2021-05-19T08:21:12Z
2024-03-21T12:28:49Z
https://github.com/yasm/yasm/issues/165
895,142,015
165
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-7306d-inc_fopen-heap-buffer-overflow ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==19224==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x603000009cea at pc 0x7f3f6962c06e bp 0x7ffce951a4d0 sp 0x7ffce9519c78 WRITE of size 23 at 0x603000009cea thread T0 #0 0x7f3f6962c06d in strcat (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x7306d) #1 0x7f3f65bb8458 in strcat /usr/include/x86_64-linux-gnu/bits/string3.h:148 #2 0x7f3f65bb8458 in inc_fopen test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:1835 #3 0x7f3f65bb8458 in do_directive test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:2737 #4 0x7f3f65bc0333 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5083 #5 0x7f3f65ba9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #6 0x7f3f65b9b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #7 0x7f3f65b8f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #8 0x7f3f65b8f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #9 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #10 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #11 0x7f3f68d9782f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #12 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) 0x603000009cea is located 0 bytes to the right of 26-byte region [0x603000009cd0,0x603000009cea) allocated by thread T0 here: #0 0x7f3f69651602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7f3f693a2769 in def_xmalloc test/yasm-uaf/SRC_asan/libyasm/xmalloc.c:69 #2 0x7f3f65bb840c in inc_fopen test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:1823 #3 0x7f3f65bb840c in do_directive test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:2737 #4 0x7f3f65bc0333 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5083 #5 0x7f3f65ba9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #6 0x7f3f65b9b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #7 0x7f3f65b8f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #8 0x7f3f65b8f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #9 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #10 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #11 0x7f3f68d9782f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) SUMMARY: AddressSanitizer: heap-buffer-overflow ??:0 strcat Shadow bytes around the buggy address: 0x0c067fff9340: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff9350: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff9360: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c067fff9370: fa fa fa fa fa fa fd fd fd fa fa fa fd fd fd fa 0x0c067fff9380: fa fa fd fd fd fa fa fa fd fd fd fa fa fa fd fd =>0x0c067fff9390: fd fa fa fa fd fd fd fa fa fa 00 00 00[02]fa fa 0x0c067fff93a0: fd fd fd fa fa fa fd fd fd fa fa fa fd fd fd fa 0x0c067fff93b0: fa fa fd fd fd fa fa fa fd fd fd fa fa fa fd fd 0x0c067fff93c0: fd fa fa fa fd fd fd fa fa fa fd fd fd fa fa fa 0x0c067fff93d0: fd fd fd fa fa fa fd fd fd fa fa fa fd fd fd fa 0x0c067fff93e0: fa fa fd fd fd fa fa fa fd fd fd fa fa fa fd fd 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 Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 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 ==19224==ABORTING ```
AddressSanitizer: heap-buffer-overflow in inc_fopen() modules/preprocs/nasm/nasm-pp.c:1835
https://api.github.com/repos/yasm/yasm/issues/164/comments
4
2021-05-19T08:20:09Z
2022-12-14T17:47:19Z
https://github.com/yasm/yasm/issues/164
895,140,978
164
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-5020-pp_getline-UAF ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==18582==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e00000ccb8 at pc 0x7f24ad5c6232 bp 0x7ffdbe2b8fb0 sp 0x7ffdbe2b8fa0 READ of size 4 at 0x60e00000ccb8 thread T0 #0 0x7f24ad5c6231 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5024 #1 0x7f24ad5a9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #2 0x7f24ad59b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #3 0x7f24ad58f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #4 0x7f24ad58f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #5 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #6 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #7 0x7f24b06e082f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #8 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) 0x60e00000ccb8 is located 152 bytes inside of 160-byte region [0x60e00000cc20,0x60e00000ccc0) freed by thread T0 here: #0 0x7f24b0f9a2ca in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x982ca) #1 0x7f24ad5bfd48 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5009 #2 0x7f24ad5a9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #3 0x7f24ad59b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #4 0x7f24ad58f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #5 0x7f24ad58f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #6 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #7 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #8 0x7f24b06e082f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) previously allocated by thread T0 here: #0 0x7f24b0f9a602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7f24b0ceb769 in def_xmalloc test/yasm-uaf/SRC_asan/libyasm/xmalloc.c:69 #2 0x7f24ad5b500b in do_directive test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:3211 #3 0x7f24ad5c0333 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5083 #4 0x7f24ad5a9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #5 0x7f24ad59b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #6 0x7f24ad58f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #7 0x7f24ad58f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #8 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #9 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #10 0x7f24b06e082f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) SUMMARY: AddressSanitizer: heap-use-after-free test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5024 pp_getline Shadow bytes around the buggy address: 0x0c1c7fff9940: fa fa fa fa fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff9950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff9960: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd 0x0c1c7fff9970: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa 0x0c1c7fff9980: fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd =>0x0c1c7fff9990: fd fd fd fd fd fd fd[fd]fa fa fa fa fa fa fa fa 0x0c1c7fff99a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff99b0: 00 00 00 00 fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff99c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff99d0: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00 0x0c1c7fff99e0: 00 00 00 00 00 00 00 00 00 00 00 00 fa fa fa 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 Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 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 ==18582==ABORTING ```
AddressSanitizer: heap-use-after-free in pp_getline() modules/preprocs/nasm/nasm-pp.c:5024
https://api.github.com/repos/yasm/yasm/issues/163/comments
1
2021-05-19T08:19:19Z
2024-03-21T12:37:57Z
https://github.com/yasm/yasm/issues/163
895,140,170
163
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-4826-error-UAF ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==17967==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e00000cd08 at pc 0x7f820a4aa94b bp 0x7ffd4c279450 sp 0x7ffd4c279440 READ of size 8 at 0x60e00000cd08 thread T0 #0 0x7f820a4aa94a in error test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:4830 #1 0x7f820a4aceaf in tokenise test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:1352 #2 0x7f820a4c0300 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5037 #3 0x7f820a4a9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #4 0x7f820a49b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #5 0x7f820a48f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #6 0x7f820a48f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #7 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #8 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #9 0x7f820d6ae82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #10 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) 0x60e00000cd08 is located 8 bytes inside of 160-byte region [0x60e00000cd00,0x60e00000cda0) freed by thread T0 here: #0 0x7f820df682ca in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x982ca) #1 0x7f820a4bfd48 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5009 #2 0x7f820a4a9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #3 0x7f820a49b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #4 0x7f820a48f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #5 0x7f820a48f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #6 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #7 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #8 0x7f820d6ae82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) previously allocated by thread T0 here: #0 0x7f820df68602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7f820dcb9769 in def_xmalloc test/yasm-uaf/SRC_asan/libyasm/xmalloc.c:69 #2 0x7f820a4b500b in do_directive test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:3211 #3 0x7f820a4c0333 in pp_getline test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:5083 #4 0x7f820a4a9d46 in nasm_preproc_get_line test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-preproc.c:198 #5 0x7f820a49b2ac in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:218 #6 0x7f820a48f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #7 0x7f820a48f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #8 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #9 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #10 0x7f820d6ae82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) SUMMARY: AddressSanitizer: heap-use-after-free test/yasm-uaf/SRC_asan/modules/preprocs/nasm/nasm-pp.c:4830 error Shadow bytes around the buggy address: 0x0c1c7fff9950: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c1c7fff9960: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c1c7fff9970: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c1c7fff9980: fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd 0x0c1c7fff9990: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa =>0x0c1c7fff99a0: fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c1c7fff99b0: fd fd fd fd fa fa fa fa fa fa fa fa 00 00 00 00 0x0c1c7fff99c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c1c7fff99d0: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00 0x0c1c7fff99e0: 00 00 00 00 00 00 00 00 00 00 00 00 fa fa fa fa 0x0c1c7fff99f0: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 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 Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 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 ==17967==ABORTING ```
AddressSanitizer: heap-use-after-free in error() modules/preprocs/nasm/nasm-pp.c:4830
https://api.github.com/repos/yasm/yasm/issues/162/comments
1
2021-05-19T08:17:11Z
2024-03-21T12:39:00Z
https://github.com/yasm/yasm/issues/162
895,137,925
162
[ "yasm", "yasm" ]
System info: Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c) I think it is probably a similar issue as [#149](https://github.com/yasm/yasm/issues/149) Compile Command: ``` $ ./autogen.sh make distclean CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared make -j make install ``` Run Command: ``` $ yasm $POC ``` POC file: https://github.com/Clingto/POC/blob/master/MSA/yasm/yasm-415-yasm_intnum_destroy-UAF ASAN info: ```C yasm: file name already has no extension: output will be in `yasm.out' ================================================================= ==16102==ERROR: AddressSanitizer: heap-use-after-free on address 0x602000007098 at pc 0x7ffa04efacb7 bp 0x7fff5b056900 sp 0x7fff5b0568f0 READ of size 4 at 0x602000007098 thread T0 #0 0x7ffa04efacb6 in yasm_intnum_destroy test/yasm-uaf/SRC_asan/libyasm/intnum.c:415 #1 0x7ffa04ee7e69 in expr_delete_term test/yasm-uaf/SRC_asan/libyasm/expr.c:1017 #2 0x7ffa04ee7e69 in expr_simplify_identity test/yasm-uaf/SRC_asan/libyasm/expr.c:582 #3 0x7ffa04ee8e3c in expr_level_op test/yasm-uaf/SRC_asan/libyasm/expr.c:700 #4 0x7ffa04eea5d1 in expr_level_tree test/yasm-uaf/SRC_asan/libyasm/expr.c:880 #5 0x7ffa04eea546 in expr_level_tree test/yasm-uaf/SRC_asan/libyasm/expr.c:864 #6 0x7ffa04eea546 in expr_level_tree test/yasm-uaf/SRC_asan/libyasm/expr.c:864 #7 0x7ffa04eeb686 in yasm_expr__level_tree test/yasm-uaf/SRC_asan/libyasm/expr.c:906 #8 0x7ffa04eeeb52 in yasm_expr_get_intnum test/yasm-uaf/SRC_asan/libyasm/expr.c:1261 #9 0x7ffa04ed9c03 in yasm_bc_create_data test/yasm-uaf/SRC_asan/libyasm/bc-data.c:292 #10 0x7ffa01795e6e in parse_exp test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:669 #11 0x7ffa0179b89f in parse_exp test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:258 #12 0x7ffa0179b89f in parse_line test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:289 #13 0x7ffa0179b89f in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:231 #14 0x7ffa0178f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #15 0x7ffa0178f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #16 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #17 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #18 0x7ffa0490b82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #19 0x403ee8 in _start ( test/yasm-uaf/bin_asan/bin/yasm+0x403ee8) 0x602000007098 is located 8 bytes inside of 16-byte region [0x602000007090,0x6020000070a0) freed by thread T0 here: #0 0x7ffa051c52ca in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x982ca) #1 0x7ffa04ee887c in expr_level_op test/yasm-uaf/SRC_asan/libyasm/expr.c:689 #2 0x7ffa04eea5d1 in expr_level_tree test/yasm-uaf/SRC_asan/libyasm/expr.c:880 #3 0x7ffa04eea546 in expr_level_tree test/yasm-uaf/SRC_asan/libyasm/expr.c:864 #4 0x7ffa04eea546 in expr_level_tree test/yasm-uaf/SRC_asan/libyasm/expr.c:864 #5 0x7ffa04eeb686 in yasm_expr__level_tree test/yasm-uaf/SRC_asan/libyasm/expr.c:906 #6 0x7ffa04eeeb52 in yasm_expr_get_intnum test/yasm-uaf/SRC_asan/libyasm/expr.c:1261 #7 0x7ffa04ed9c03 in yasm_bc_create_data test/yasm-uaf/SRC_asan/libyasm/bc-data.c:292 #8 0x7ffa01795e6e in parse_exp test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:669 #9 0x7ffa0179b89f in parse_exp test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:258 #10 0x7ffa0179b89f in parse_line test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:289 #11 0x7ffa0179b89f in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:231 #12 0x7ffa0178f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #13 0x7ffa0178f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #14 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #15 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #16 0x7ffa0490b82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) previously allocated by thread T0 here: #0 0x7ffa051c5602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7ffa04f16769 in def_xmalloc test/yasm-uaf/SRC_asan/libyasm/xmalloc.c:69 #2 0x7ffa04efab26 in yasm_intnum_copy test/yasm-uaf/SRC_asan/libyasm/intnum.c:397 #3 0x7ffa04ee33e4 in expr_item_copy test/yasm-uaf/SRC_asan/libyasm/expr.c:975 #4 0x7ffa04ee33e4 in yasm_expr__copy_except test/yasm-uaf/SRC_asan/libyasm/expr.c:1006 #5 0x7ffa04eebc13 in expr_expand_equ test/yasm-uaf/SRC_asan/libyasm/expr.c:834 #6 0x7ffa04eebc13 in expr_expand_equ test/yasm-uaf/SRC_asan/libyasm/expr.c:843 #7 0x7ffa04eebc13 in expr_expand_equ test/yasm-uaf/SRC_asan/libyasm/expr.c:839 #8 0x7ffa04eebc13 in yasm_expr__level_tree test/yasm-uaf/SRC_asan/libyasm/expr.c:905 #9 0x7ffa04eeeb52 in yasm_expr_get_intnum test/yasm-uaf/SRC_asan/libyasm/expr.c:1261 #10 0x7ffa04ed9c03 in yasm_bc_create_data test/yasm-uaf/SRC_asan/libyasm/bc-data.c:292 #11 0x7ffa01795e6e in parse_exp test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:669 #12 0x7ffa0179b89f in parse_exp test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:258 #13 0x7ffa0179b89f in parse_line test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:289 #14 0x7ffa0179b89f in nasm_parser_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parse.c:231 #15 0x7ffa0178f36b in nasm_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:66 #16 0x7ffa0178f36b in nasm_parser_do_parse test/yasm-uaf/SRC_asan/modules/parsers/nasm/nasm-parser.c:83 #17 0x402c84 in do_assemble test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:521 #18 0x402c84 in main test/yasm-uaf/SRC_asan/frontends/yasm/yasm.c:753 #19 0x7ffa0490b82f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) SUMMARY: AddressSanitizer: heap-use-after-free test/yasm-uaf/SRC_asan/libyasm/intnum.c:415 yasm_intnum_destroy Shadow bytes around the buggy address: 0x0c047fff8dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8dd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8de0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8df0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c047fff8e00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa =>0x0c047fff8e10: fa fa fd[fd]fa fa 00 00 fa fa 00 00 fa fa fd fa 0x0c047fff8e20: fa fa fd fa fa fa 07 fa fa fa fd fa fa fa fd fa 0x0c047fff8e30: fa fa 07 fa fa fa 00 00 fa fa 00 00 fa fa 07 fa 0x0c047fff8e40: fa fa fd fa fa fa fd fd fa fa fd fa fa fa fd fa 0x0c047fff8e50: fa fa fd fa fa fa 03 fa fa fa 00 00 fa fa 00 00 0x0c047fff8e60: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fd 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 Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 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 ==16102==ABORTING ```
AddressSanitizer: heap-use-after-free in yasm_intnum_destroy() libyasm/intnum.c:415
https://api.github.com/repos/yasm/yasm/issues/161/comments
3
2021-05-19T08:15:14Z
2024-03-21T11:56:29Z
https://github.com/yasm/yasm/issues/161
895,135,903
161
[ "yasm", "yasm" ]
Please tell me how to address the zmm registers? `helloWorld.asm:17: error: undefined symbol `zmm1' (first use)`
error: undefined symbol `zmm1'
https://api.github.com/repos/yasm/yasm/issues/159/comments
0
2021-02-03T23:06:20Z
2021-02-03T23:06:20Z
https://github.com/yasm/yasm/issues/159
800,772,221
159
[ "yasm", "yasm" ]
In current vsyasm.targets this line: `CommandLineTemplate="$(MSBuildThisFileDirectory)\vsyasm.exe -Xvc -f %(YASM.Platform) [AllOptions] [AdditionalOptions] [Inputs]"` should be cchanged to: `CommandLineTemplate="&quot;$(MSBuildThisFileDirectory)\vsyasm.exe&quot; -Xvc -f %(YASM.Platform) [AllOptions] [AdditionalOptions] [Inputs]"`
vyasm fails in folders with spaces in it
https://api.github.com/repos/yasm/yasm/issues/158/comments
8
2020-12-27T15:05:23Z
2020-12-28T19:34:12Z
https://github.com/yasm/yasm/issues/158
775,053,819
158
[ "yasm", "yasm" ]
Hi there. when running make check, I got 2/44 tests failed: 1. FAIL: modules/objfmts/elf/tests/amd64/elf_amd64_test.sh ======================================================= Test elf_amd64_test: O... +3-1/4 75% ** O: elf-rip did not match object file! 2. FAIL: modules/objfmts/elf/tests/gas64/elf_gas64_test.sh ======================================================= Test elf_gas64_test: O... +3-1/4 75% ** O: crosssect did not match object file!
make check has 2 failed tests (linux amd64)
https://api.github.com/repos/yasm/yasm/issues/157/comments
3
2020-11-10T14:28:27Z
2021-05-24T23:13:18Z
https://github.com/yasm/yasm/issues/157
739,957,551
157
[ "yasm", "yasm" ]
`endbr64` is a new psuedo-instruction (well, it's a real instruction on some CPUs that is) used for control flow information using what was previously a multibyte nop encoding: `\xf3\x0f\x1e\xfa`
No support for endbr64 instruction
https://api.github.com/repos/yasm/yasm/issues/156/comments
1
2020-08-24T19:43:05Z
2021-11-01T13:08:48Z
https://github.com/yasm/yasm/issues/156
684,918,851
156
[ "yasm", "yasm" ]
I built yasm with cmake on zsh and installed to a directory "/usr/local/git". And I could find "/usr/local/git/bin/yasm" and "/usr/local/git/lib/libyasm.dylib". I set the library path as "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib:/usr/local/git/lib" in zshrc. But yasm command cannot find libyasm.dylib. How can I fix it? ``` hoge@hoge % yasm dyld: Library not loaded: libyasm.dylib Referenced from: /usr/local/git/bin/yasm Reason: image not found zsh: abort yasm hoge@hoge % ```
"dyld: Library not loaded: libyasm.dylib" on macOS 10.15
https://api.github.com/repos/yasm/yasm/issues/155/comments
3
2020-08-06T16:08:10Z
2020-08-07T04:10:37Z
https://github.com/yasm/yasm/issues/155
674,429,183
155
[ "yasm", "yasm" ]
see my PR https://github.com/yasm/yasm/pull/148
add .note.gnu.property note section support
https://api.github.com/repos/yasm/yasm/issues/154/comments
0
2020-07-16T16:55:24Z
2020-07-16T16:56:56Z
https://github.com/yasm/yasm/issues/154
658,376,702
154
[ "yasm", "yasm" ]
Hi guys, Recently, I want to update yasm in vcpkg ([#12324](https://github.com/microsoft/vcpkg/pull/12324)) to solve some issues, but I got the error message on the pipeline machine: ``` D:\installed\x64-windows\share\vs-yasm\yasm.targets(50,5): error MSB3721: The command ""D:/downloads/tools/yasm/1.3.0.6/x64/"yasm.exe -Xvc -f win64 -o "D:\buildtrees\gmp\x64-windows-rel\adcc6b3cc4-2b6258d695.clean\SMP\obj\ReleaseDLL\x64\libgmp\addaddmul_1msb0.obj" -rraw -pgas "D:\buildtrees\gmp\x64-windows-rel\adcc6b3cc4-2b6258d695.clean\SMP\mpn\x86_64\addaddmul_1msb0.s"" exited with code -1073741515. [D:\buildtrees\gmp\x64-windows-rel\adcc6b3cc4-2b6258d695.clean\SMP\libgmp.vcxproj] ``` This command invokes symlink from other disks. If symlink is not used, this problem will not occur. Anyone can solve this issue or give me some solutions? Thanks.
yasm exits abnormally on Windows
https://api.github.com/repos/yasm/yasm/issues/153/comments
4
2020-07-09T02:41:04Z
2020-10-09T08:18:33Z
https://github.com/yasm/yasm/issues/153
653,717,823
153
[ "yasm", "yasm" ]
# Version yasm-c9db6d7 # Command ./yasm $FILE -o /tmp/foo # Bug Type stack overflow # Crash file https://github.com/natalie13m/crashes/blob/master/yasm-c9db6d7/id:000086%2Csig:11%2Csrc:015136%2B014346%2Cop:splice%2Crep:16 # Address Sanitizer output ``` AddressSanitizer:DEADLYSIGNAL ================================================================= ==17050==ERROR: AddressSanitizer: stack-overflow on address 0x7ffffbb64ff8 (pc 0x55e1edaf02d5 bp 0x7ffffbb65040 sp 0x7ffffbb64ff0 T0) #0 0x55e1edaf02d4 in parse_expr6 modules/parsers/nasm/nasm-parse.c:1335 #1 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #2 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #3 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #4 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #5 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #6 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #7 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #8 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #9 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #10 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #11 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #12 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #13 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #14 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #15 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #16 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #17 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #18 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #19 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #20 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #21 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #22 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #23 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #24 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #25 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #26 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #27 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #28 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #29 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #30 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #31 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #32 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #33 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #34 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #35 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #36 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #37 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #38 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #39 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #40 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #41 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #42 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #43 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #44 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #45 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #46 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #47 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #48 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #49 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #50 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #51 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #52 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #53 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #54 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #55 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #56 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #57 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #58 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #59 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #60 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #61 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #62 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #63 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #64 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #65 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #66 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #67 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #68 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #69 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #70 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #71 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #72 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #73 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #74 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #75 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #76 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #77 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #78 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #79 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #80 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #81 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #82 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #83 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #84 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #85 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #86 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #87 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #88 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #89 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #90 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #91 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #92 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #93 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #94 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #95 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #96 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #97 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #98 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #99 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #100 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #101 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #102 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #103 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #104 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #105 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #106 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #107 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #108 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #109 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #110 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #111 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #112 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #113 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #114 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #115 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #116 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #117 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #118 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #119 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #120 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #121 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #122 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #123 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #124 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #125 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #126 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #127 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #128 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #129 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #130 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #131 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #132 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #133 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #134 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #135 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #136 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #137 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #138 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #139 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #140 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #141 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #142 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #143 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #144 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #145 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #146 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #147 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #148 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #149 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #150 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #151 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #152 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #153 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #154 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #155 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #156 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #157 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #158 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #159 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #160 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #161 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #162 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #163 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #164 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #165 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #166 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #167 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #168 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #169 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #170 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #171 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #172 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #173 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #174 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #175 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #176 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #177 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #178 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #179 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #180 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #181 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #182 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #183 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #184 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #185 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #186 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #187 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #188 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #189 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #190 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #191 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #192 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #193 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #194 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #195 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #196 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #197 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #198 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #199 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #200 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #201 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #202 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #203 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #204 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #205 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #206 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #207 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #208 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #209 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #210 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #211 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #212 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #213 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #214 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #215 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #216 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #217 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #218 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #219 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #220 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #221 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #222 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #223 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #224 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #225 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #226 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #227 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #228 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #229 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #230 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #231 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #232 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #233 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #234 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #235 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #236 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #237 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #238 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #239 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 #240 0x55e1edaef3f8 in parse_expr0 modules/parsers/nasm/nasm-parse.c:1230 #241 0x55e1edaef236 in parse_bexpr modules/parsers/nasm/nasm-parse.c:1224 #242 0x55e1edaef076 in parse_expr modules/parsers/nasm/nasm-parse.c:1215 #243 0x55e1edaf0b5d in parse_expr6 modules/parsers/nasm/nasm-parse.c:1401 #244 0x55e1edaefe78 in parse_expr5 modules/parsers/nasm/nasm-parse.c:1305 #245 0x55e1edaefbdd in parse_expr4 modules/parsers/nasm/nasm-parse.c:1277 #246 0x55e1edaef938 in parse_expr3 modules/parsers/nasm/nasm-parse.c:1249 #247 0x55e1edaef778 in parse_expr2 modules/parsers/nasm/nasm-parse.c:1242 #248 0x55e1edaef5b8 in parse_expr1 modules/parsers/nasm/nasm-parse.c:1236 SUMMARY: AddressSanitizer: stack-overflow modules/parsers/nasm/nasm-parse.c:1335 in parse_expr6 ==17050==ABORTING ``` # Crashwalk output ---CRASH SUMMARY--- Filename: crash/id:000086,sig:11,src:015136+014346,op:splice,rep:16 SHA1: 7cc921553da37197f3ffed45abc96a969566c6d6 Classification: UNKNOWN Hash: 4a0f3ceae8f0d66f8443a7a81545fa9e.6e94e6b36bc151f5dadd0535bd9a17c8 Command: ./yasm crash/id:000086,sig:11,src:015136+014346,op:splice,rep:16 -o /tmp/foo Faulting Frame: parse_expr5 @ 0x00005555555be578: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm Disassembly: 0x00005555555be570: endbr64 0x00005555555be574: push rbp 0x00005555555be575: mov rbp,rsp => 0x00005555555be578: push r12 0x00005555555be57a: push rbx 0x00005555555be57b: sub rsp,0x30 0x00005555555be57f: mov QWORD PTR [rbp-0x38],rdi 0x00005555555be583: mov DWORD PTR [rbp-0x3c],esi Stack Head (1000 entries): parse_expr5 @ 0x00005555555be578: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr4 @ 0x00005555555be400: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr3 @ 0x00005555555be25f: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr2 @ 0x00005555555be144: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr1 @ 0x00005555555be029: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr0 @ 0x00005555555bdf0e: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_bexpr @ 0x00005555555bddf1: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr @ 0x00005555555bdcd6: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr6 @ 0x00005555555bedbb: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr5 @ 0x00005555555be597: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr4 @ 0x00005555555be400: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr3 @ 0x00005555555be25f: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr2 @ 0x00005555555be144: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr1 @ 0x00005555555be029: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_expr0 @ 0x00005555555bdf0e: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_bexpr @ 0x00005555555bddf1: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm Registers: rax=0x00007fffffffda70 rbx=0x0000000000000000 rcx=0x0000000000000000 rdx=0x0000000000000002 rsi=0x0000000000000002 rdi=0x00007fffffffda70 rbp=0x00007fffff7ff000 rsp=0x00007fffff7ff000 r8=0x00000000ffffffff r9=0x00007fffffbb6cb0 r10=0x000055555562a303 r11=0x00005555556588a8 r12=0x000055555558e7f0 r13=0x00007fffffffdd80 r14=0x0000000000000000 r15=0x0000000000000000 rip=0x00005555555be578 efl=0x0000000000010202 cs=0x0000000000000033 ss=0x000000000000002b ds=0x0000000000000000 es=0x0000000000000000 fs=0x0000000000000000 gs=0x0000000000000000 Extra Data: Description: Access violation Short description: AccessViolation (21/22) Explanation: The target crashed due to an access violation but there is not enough additional information available to determine exploitability. ---END SUMMARY---
Stack overflow in parse_expr6(5,4,3,2,1) modules/parsers/nasm/nasm-parse.c
https://api.github.com/repos/yasm/yasm/issues/152/comments
1
2020-06-13T04:46:15Z
2021-11-01T11:54:03Z
https://github.com/yasm/yasm/issues/152
638,095,591
152
[ "yasm", "yasm" ]
# Version yasm-c9db6d7 # Command ./yasm $FILE -o /tmp/foo # Bug Type read memory access violation on the zero page # Crash file https://github.com/natalie13m/crashes/blob/master/yasm-c9db6d7/id:000104%2Csig:11%2Csrc:005124%2B007559%2Cop:splice%2Crep:64 # Address Sanitizer output AddressSanitizer:DEADLYSIGNAL ================================================================= ==15694==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000001 (pc 0x5591c002eb1f bp 0x7ffe17fb59b0 sp 0x7ffe17fb5880 T0) ==15694==The signal is caused by a READ memory access. ==15694==Hint: address points to the zero page. #0 0x5591c002eb1e in expand_mmac_params modules/preprocs/nasm/nasm-pp.c:3861 #1 0x5591c0037109 in pp_getline modules/preprocs/nasm/nasm-pp.c:5078 #2 0x5591c0014980 in nasm_preproc_get_line modules/preprocs/nasm/nasm-preproc.c:198 #3 0x5591c0009239 in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:219 #4 0x5591c0007cc2 in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #5 0x5591c0007e55 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #6 0x5591bffa04c9 in do_assemble frontends/yasm/yasm.c:521 #7 0x5591bffa1268 in main frontends/yasm/yasm.c:753 #8 0x7ff5f090e1e2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x271e2) #9 0x5591bff9eb9d in _start (/home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm-asan+0xa4b9d) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV modules/preprocs/nasm/nasm-pp.c:3861 in expand_mmac_params ==15694==ABORTING # Crashwalk output ---CRASH SUMMARY--- Filename: crash/id:000104,sig:11,src:005124+007559,op:splice,rep:64 SHA1: 929e402d195f4fd25a1538d9844dd677adec647f Classification: PROBABLY_NOT_EXPLOITABLE Hash: f21d77c9ce98780c34460d739987cdbe.e085dc30be95c0c69044d2f8aed53429 Command: ./yasm crash/id:000104,sig:11,src:005124+007559,op:splice,rep:64 -o /tmp/foo Faulting Frame: expand_mmac_params @ 0x00005555555ca3ff: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm Disassembly: 0x00005555555ca3e7: cmp eax,0x4 0x00005555555ca3ea: jne 0x5555555cac27 <expand_mmac_params+2180> 0x00005555555ca3f0: mov rax,QWORD PTR [rbp-0xa8] 0x00005555555ca3f7: mov rax,QWORD PTR [rax+0x8] 0x00005555555ca3fb: add rax,0x1 => 0x00005555555ca3ff: movzx eax,BYTE PTR [rax] 0x00005555555ca402: cmp al,0x2b 0x00005555555ca404: je 0x5555555ca41c <expand_mmac_params+121> 0x00005555555ca406: mov rax,QWORD PTR [rbp-0xa8] 0x00005555555ca40d: mov rax,QWORD PTR [rax+0x8] Stack Head (8 entries): expand_mmac_params @ 0x00005555555ca3ff: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm pp_getline @ 0x00005555555cd02f: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm nasm_preproc_get_line @ 0x00005555555c019a: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm nasm_parser_parse @ 0x00005555555bab9f: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm nasm_do_parse @ 0x00005555555ba1f5: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm nasm_parser_do_parse @ 0x00005555555ba28d: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm do_assemble @ 0x000055555558f4b5: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm main @ 0x000055555558fdd0: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm Registers: rax=0x0000000000000001 rbx=0x0000000000000000 rcx=0x0000000000000007 rdx=0x000055555566f270 rsi=0x0000555555672230 rdi=0x00007ffff7faebf0 rbp=0x00007fffffffd8e0 rsp=0x00007fffffffd830 r8=0x0000000000000006 r9=0x00007ffff7f9bb80 r10=0x0000000000000007 r11=0x0000000000000007 r12=0x000055555558e7f0 r13=0x00007fffffffdd80 r14=0x0000000000000000 r15=0x0000000000000000 rip=0x00005555555ca3ff efl=0x0000000000010202 cs=0x0000000000000033 ss=0x000000000000002b ds=0x0000000000000000 es=0x0000000000000000 fs=0x0000000000000000 gs=0x0000000000000000 Extra Data: Description: Access violation near NULL on source operand Short description: SourceAvNearNull (16/22) Explanation: The target crashed on an access violation at an address matching the source operand of the current instruction. This likely indicates a read access violation, which may mean the application crashed on a simple NULL dereference to data structure that has no immediate effect on control of the processor. ---END SUMMARY---
Access violation near NULL on source operand in expand_mmac_params modules/preprocs/nasm/nasm-pp.c:3861
https://api.github.com/repos/yasm/yasm/issues/151/comments
0
2020-06-13T04:42:53Z
2020-06-13T04:42:53Z
https://github.com/yasm/yasm/issues/151
638,095,211
151
[ "yasm", "yasm" ]
# Version yasm-c9db6d7 # Command ./yasm $FILE -o /tmp/foo # Bug Type read memory access violation on zero page # Crash file https://github.com/natalie13m/crashes/blob/master/yasm-c9db6d7/id:000101%2Csig:11%2Csrc:015858%2Cop:havoc%2Crep:64 # Address Sanitizer output ``` AddressSanitizer:DEADLYSIGNAL ================================================================= ==13667==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x557a14db8267 bp 0x7fff6e93acd0 sp 0x7fff6e93aca0 T0) ==13667==The signal is caused by a READ memory access. ==13667==Hint: address points to the zero page. #0 0x557a14db8266 in BitVector_Block_Store libyasm/bitvect.c:3261 #1 0x557a14dc97e7 in yasm_intnum_get_sized libyasm/intnum.c:803 #2 0x557a14de859d in yasm_x86__intnum_tobytes modules/arch/x86/x86bc.c:1060 #3 0x557a14e9f3d1 in yasm_bc_create_data libyasm/bc-data.c:364 #4 0x557a14e1006d in parse_exp modules/parsers/nasm/nasm-parse.c:669 #5 0x557a14e0d354 in parse_line modules/parsers/nasm/nasm-parse.c:289 #6 0x557a14e0cc30 in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:231 #7 0x557a14e0bcc2 in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #8 0x557a14e0be55 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #9 0x557a14da44c9 in do_assemble frontends/yasm/yasm.c:521 #10 0x557a14da5268 in main frontends/yasm/yasm.c:753 #11 0x7f9d1b0351e2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x271e2) #12 0x557a14da2b9d in _start (/home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm-asan+0xa4b9d) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV libyasm/bitvect.c:3261 in BitVector_Block_Store ==13667==ABORTING ``` # Crashwalk output ---CRASH SUMMARY--- Filename: crash/id:000101,sig:11,src:015858,op:havoc,rep:64 SHA1: f3f22117622a2081b831c9779cbc4f524606b681 Classification: PROBABLY_NOT_EXPLOITABLE Hash: 87592677736c7d7f4e2466a45b254eb3.94d9964d5aeadbe09bea67599fb8a0b1 Command: ./yasm crash/id:000101,sig:11,src:015858,op:havoc,rep:64 -o /tmp/foo Faulting Frame: BitVector_Block_Store @ 0x000055555559918e: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm Disassembly: 0x0000555555599179: mov DWORD PTR [rbp-0x8],0x0 0x0000555555599180: jmp 0x5555555991a8 <BitVector_Block_Store+101> 0x0000555555599182: mov rax,QWORD PTR [rbp-0x20] 0x0000555555599186: lea rdx,[rax+0x1] 0x000055555559918a: mov QWORD PTR [rbp-0x20],rdx => 0x000055555559918e: movzx eax,BYTE PTR [rax] 0x0000555555599191: movzx edx,al 0x0000555555599194: mov eax,DWORD PTR [rbp-0x8] 0x0000555555599197: mov ecx,eax 0x0000555555599199: shl edx,cl Stack Head (11 entries): BitVector_Block_Store @ 0x000055555559918e: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm yasm_intnum_get_sized @ 0x00005555555a0454: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm yasm_x86__intnum_tobytes @ 0x00005555555ac661: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm yasm_bc_create_data @ 0x00005555555f555b: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_exp @ 0x00005555555bc0ad: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm parse_line @ 0x00005555555bac03: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm nasm_parser_parse @ 0x00005555555ba93e: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm nasm_do_parse @ 0x00005555555ba1f5: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm nasm_parser_do_parse @ 0x00005555555ba28d: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm do_assemble @ 0x000055555558f4b5: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm main @ 0x000055555558fdd0: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm Registers: rax=0x0000000000000002 rbx=0x0000000000000000 rcx=0x0000000000000002 rdx=0x0000000000000003 rsi=0x0000000000000002 rdi=0x000055555566941c rbp=0x00007fffffffd720 rsp=0x00007fffffffd720 r8=0x0000000000000000 r9=0x0000000000000000 r10=0x00005555555ac613 r11=0x00007ffff7f9bbe0 r12=0x000055555558e7f0 r13=0x00007fffffffdd80 r14=0x0000000000000000 r15=0x0000000000000000 rip=0x000055555559918e efl=0x0000000000010283 cs=0x0000000000000033 ss=0x000000000000002b ds=0x0000000000000000 es=0x0000000000000000 fs=0x0000000000000000 gs=0x0000000000000000 Extra Data: Description: Access violation near NULL on source operand Short description: SourceAvNearNull (16/22) Explanation: The target crashed on an access violation at an address matching the source operand of the current instruction. This likely indicates a read access violation, which may mean the application crashed on a simple NULL dereference to data structure that has no immediate effect on control of the processor. ---END SUMMARY---
Access violation near NULL on source operand in BitVector_Block_Store libyasm/bitvect.c:3261
https://api.github.com/repos/yasm/yasm/issues/150/comments
1
2020-06-13T04:35:42Z
2021-11-01T11:55:53Z
https://github.com/yasm/yasm/issues/150
638,094,456
150
[ "yasm", "yasm" ]
# Version yasm-c9db6d7 # Command ./yasm $FILE -o /tmp/foo # Bug Type: heap-use-after-free # Crash file https://github.com/natalie13m/crashes/blob/master/yasm-c9db6d7/id:000053%2Csig:11%2Csrc:014975%2Cop:havoc%2Crep:4 #Address Sanitizer Output ``` ================================================================= ==8969==ERROR: AddressSanitizer: heap-use-after-free on address 0x6020000076d8 at pc 0x563be1b5cb00 bp 0x7ffc15fc6690 sp 0x7ffc15fc6680 READ of size 4 at 0x6020000076d8 thread T0 #0 0x563be1b5caff in yasm_intnum_destroy libyasm/intnum.c:415 #1 0x563be1c3fbb0 in expr_delete_term libyasm/expr.c:1017 #2 0x563be1c3cb16 in expr_simplify_identity libyasm/expr.c:582 #3 0x563be1c3da8d in expr_level_op libyasm/expr.c:701 #4 0x563be1c3f132 in expr_level_tree libyasm/expr.c:880 #5 0x563be1c3f19c in expr_level_tree libyasm/expr.c:886 #6 0x563be1c3eef0 in expr_level_tree libyasm/expr.c:864 #7 0x563be1c3eef0 in expr_level_tree libyasm/expr.c:864 #8 0x563be1c3eef0 in expr_level_tree libyasm/expr.c:864 #9 0x563be1c3f2f6 in yasm_expr__level_tree libyasm/expr.c:906 #10 0x563be1bfee40 in bin_objfmt_output_value modules/objfmts/bin/bin-objfmt.c:954 #11 0x563be1c3328d in bc_data_tobytes libyasm/bc-data.c:226 #12 0x563be1c39630 in yasm_bc_tobytes libyasm/bytecode.c:341 #13 0x563be1bff0bb in bin_objfmt_output_bytecode modules/objfmts/bin/bin-objfmt.c:984 #14 0x563be1b63bc1 in yasm_section_bcs_traverse libyasm/section.c:637 #15 0x563be1bffabc in bin_objfmt_output_section modules/objfmts/bin/bin-objfmt.c:1082 #16 0x563be1b63534 in yasm_object_sections_traverse libyasm/section.c:544 #17 0x563be1c01b19 in bin_objfmt_output modules/objfmts/bin/bin-objfmt.c:1352 #18 0x563be1b397ab in do_assemble frontends/yasm/yasm.c:548 #19 0x563be1b3a268 in main frontends/yasm/yasm.c:753 #20 0x7f92c64fa1e2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x271e2) #21 0x563be1b37b9d in _start (/home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm-asan+0xa4b9d) 0x6020000076d8 is located 8 bytes inside of 16-byte region [0x6020000076d0,0x6020000076e0) freed by thread T0 here: #0 0x7f92c67d16ef in __interceptor_free (/lib/x86_64-linux-gnu/libasan.so.5+0x10d6ef) #1 0x563be1b747c0 in def_xfree libyasm/xmalloc.c:113 #2 0x563be1b5cb6f in yasm_intnum_destroy libyasm/intnum.c:417 #3 0x563be1c3d929 in expr_level_op libyasm/expr.c:689 #4 0x563be1c3f132 in expr_level_tree libyasm/expr.c:880 #5 0x563be1c3f19c in expr_level_tree libyasm/expr.c:886 #6 0x563be1c3eef0 in expr_level_tree libyasm/expr.c:864 #7 0x563be1c3eef0 in expr_level_tree libyasm/expr.c:864 #8 0x563be1c3eef0 in expr_level_tree libyasm/expr.c:864 #9 0x563be1c3f2f6 in yasm_expr__level_tree libyasm/expr.c:906 #10 0x563be1bfee40 in bin_objfmt_output_value modules/objfmts/bin/bin-objfmt.c:954 #11 0x563be1c3328d in bc_data_tobytes libyasm/bc-data.c:226 #12 0x563be1c39630 in yasm_bc_tobytes libyasm/bytecode.c:341 #13 0x563be1bff0bb in bin_objfmt_output_bytecode modules/objfmts/bin/bin-objfmt.c:984 #14 0x563be1b63bc1 in yasm_section_bcs_traverse libyasm/section.c:637 #15 0x563be1bffabc in bin_objfmt_output_section modules/objfmts/bin/bin-objfmt.c:1082 #16 0x563be1b63534 in yasm_object_sections_traverse libyasm/section.c:544 #17 0x563be1c01b19 in bin_objfmt_output modules/objfmts/bin/bin-objfmt.c:1352 #18 0x563be1b397ab in do_assemble frontends/yasm/yasm.c:548 #19 0x563be1b3a268 in main frontends/yasm/yasm.c:753 #20 0x7f92c64fa1e2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x271e2) previously allocated by thread T0 here: #0 0x7f92c67d1ae8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dae8) #1 0x563be1b746a3 in def_xmalloc libyasm/xmalloc.c:69 #2 0x563be1b5c4aa in yasm_intnum_create_int libyasm/intnum.c:328 #3 0x563be1c3bfb6 in expr_xform_neg_helper libyasm/expr.c:431 #4 0x563be1c3c24a in expr_xform_neg libyasm/expr.c:466 #5 0x563be1c3edfd in expr_level_tree libyasm/expr.c:857 #6 0x563be1c3eef0 in expr_level_tree libyasm/expr.c:864 #7 0x563be1c3eef0 in expr_level_tree libyasm/expr.c:864 #8 0x563be1c3eef0 in expr_level_tree libyasm/expr.c:864 #9 0x563be1c3eef0 in expr_level_tree libyasm/expr.c:864 #10 0x563be1c3f2f6 in yasm_expr__level_tree libyasm/expr.c:906 #11 0x563be1c40d86 in yasm_expr_get_intnum libyasm/expr.c:1261 #12 0x563be1c33a5a in yasm_bc_create_data libyasm/bc-data.c:292 #13 0x563be1ba506d in parse_exp modules/parsers/nasm/nasm-parse.c:669 #14 0x563be1ba2354 in parse_line modules/parsers/nasm/nasm-parse.c:289 #15 0x563be1ba1c30 in nasm_parser_parse modules/parsers/nasm/nasm-parse.c:231 #16 0x563be1ba0cc2 in nasm_do_parse modules/parsers/nasm/nasm-parser.c:66 #17 0x563be1ba0e55 in nasm_parser_do_parse modules/parsers/nasm/nasm-parser.c:83 #18 0x563be1b394c9 in do_assemble frontends/yasm/yasm.c:521 #19 0x563be1b3a268 in main frontends/yasm/yasm.c:753 #20 0x7f92c64fa1e2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x271e2) SUMMARY: AddressSanitizer: heap-use-after-free libyasm/intnum.c:415 in yasm_intnum_destroy Shadow bytes around the buggy address: 0x0c047fff8e80: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa 0x0c047fff8e90: fa fa fd fa fa fa fd fa fa fa fd fa fa fa fd fa 0x0c047fff8ea0: fa fa fd fa fa fa fd fd fa fa fd fd fa fa 02 fa 0x0c047fff8eb0: fa fa 00 00 fa fa 02 fa fa fa 00 00 fa fa 02 fa 0x0c047fff8ec0: fa fa 00 00 fa fa 00 00 fa fa 02 fa fa fa 00 00 =>0x0c047fff8ed0: fa fa 00 00 fa fa fd fd fa fa fd[fd]fa fa fd fd 0x0c047fff8ee0: fa fa fd fd fa fa fd fd fa fa fd fd fa fa fd fd 0x0c047fff8ef0: fa fa fd fd fa fa fd fd fa fa fd fd fa fa fd fd 0x0c047fff8f00: fa fa fd fd fa fa fd fd fa fa fd fd fa fa fd fd 0x0c047fff8f10: fa fa fd fd fa fa fd fd fa fa fd fd fa fa fd fd 0x0c047fff8f20: fa fa fd fd fa fa fd fd fa fa fd fd fa fa fd fd 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 Shadow gap: cc ==8969==ABORTING ``` # Crashwalk output ---CRASH SUMMARY--- Filename: crash/id:000053,sig:11,src:014975,op:havoc,rep:4 SHA1: 8cc51b142a8b90c17f10bf7346a71a299ee81750 Classification: EXPLOITABLE Hash: 3b8255b6395b61bec677200e629cc277.c02d1951c102e9fc734b72c2a91af469 Command: ./yasm crash/id:000053,sig:11,src:014975,op:havoc,rep:4 -o /tmp/foo Faulting Frame: def_xfree @ 0x00005555555a8c6b: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm Disassembly: 0x00007ffff7df73da: xor edx,edx 0x00007ffff7df73dc: mov rsi,r9 0x00007ffff7df73df: mov edi,0x2 0x00007ffff7df73e4: mov eax,0xe 0x00007ffff7df73e9: syscall => 0x00007ffff7df73eb: mov rax,QWORD PTR [rsp+0x108] 0x00007ffff7df73f3: xor rax,QWORD PTR fs:0x28 0x00007ffff7df73fc: jne 0x7ffff7df7424 <__GI_raise+260> 0x00007ffff7df73fe: mov eax,r8d 0x00007ffff7df7401: add rsp,0x118 Stack Head (26 entries): __GI_raise @ 0x00007ffff7df73eb: in (BL) __GI_abort @ 0x00007ffff7dd6899: in (BL) __libc_message @ 0x00007ffff7e4138e: in (BL) malloc_printerr @ 0x00007ffff7e494dc: in (BL) _int_free @ 0x00007ffff7e4b13d: in (BL) def_xfree @ 0x00005555555a8c6b: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm yasm_intnum_destroy @ 0x000055555559f510: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm expr_delete_term @ 0x00005555555f9a1d: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm expr_simplify_identity @ 0x00005555555f8a57: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm expr_level_op @ 0x00005555555f8eb2: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm expr_level_tree @ 0x00005555555f9628: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm expr_level_tree @ 0x00005555555f9692: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm expr_level_tree @ 0x00005555555f9579: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm expr_level_tree @ 0x00005555555f9579: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm expr_level_tree @ 0x00005555555f9579: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm yasm_expr__level_tree @ 0x00005555555f972e: in /home/natalie/Desktop/research/Bug/yasm-c9db6d7/yasm Registers: rax=0x0000000000000000 rbx=0x00007ffff7fa3580 rcx=0x00007ffff7df73eb rdx=0x0000000000000000 rsi=0x00007fffffffd0b0 rdi=0x0000000000000002 rbp=0x00007fffffffd400 rsp=0x00007fffffffd0b0 r8=0x0000000000000000 r9=0x00007fffffffd0b0 r10=0x0000000000000008 r11=0x0000000000000246 r12=0x00007fffffffd320 r13=0x0000000000000010 r14=0x00007ffff7ffb000 r15=0x0000000000000002 rip=0x00007ffff7df73eb efl=0x0000000000000246 cs=0x0000000000000033 ss=0x000000000000002b ds=0x0000000000000000 es=0x0000000000000000 fs=0x0000000000000000 gs=0x0000000000000000 Extra Data: Description: Heap error Short description: HeapError (10/22) Explanation: The target's backtrace indicates that libc has detected a heap error or that the target was executing a heap function when it stopped. This could be due to heap corruption, passing a bad pointer to a heap function such as free(), etc. Since heap errors might include buffer overflows, use-after-free situations, etc. they are generally considered exploitable. ---END SUMMARY---
heap-use-after-free in yasm_intnum_destroy libyasm/intnum.c:415
https://api.github.com/repos/yasm/yasm/issues/149/comments
1
2020-06-13T04:32:19Z
2021-11-01T11:55:15Z
https://github.com/yasm/yasm/issues/149
638,094,099
149
[ "yasm", "yasm" ]
As Python 2 reached EOL, support for Python 3 will be great.
support Python 3
https://api.github.com/repos/yasm/yasm/issues/143/comments
1
2020-02-10T09:34:15Z
2020-02-10T10:00:49Z
https://github.com/yasm/yasm/issues/143
562,433,867
143
[ "yasm", "yasm" ]
While using yasm 1.3 some errors happen. Poc files can be found [here](https://tortall.lighthouseapp.com/projects/78676/tickets/380-null-ponter-dereference-happends-in-expand_mmac_params-nasmnasm-ppc#ticket-380-3) ### Error One yasm-1.3 has a null pointer dereference or heap buffer over-read in expand_mmac_params in nasm/nasm-pp.c for insufficient input. ``` cs@ubuntu:~/poc1$ yasm -f bin poc1 -o 1.out Segmentation fault (core dumped) ``` ``` cs@ubuntu:~/poc$ gdb --args yasm -f bin poc1 -o 1.out GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from yasm...done. (gdb) r Starting program: /usr/local/bin/yasm -f bin poc1 -o 1.out Program received signal SIGSEGV, Segmentation fault. 0x0000000000426559 in expand_mmac_params (tline=0x7ffff7fc2830, tline@entry=0x7ffff7fc27f0) at modules/preprocs/nasm/nasm-pp.c:3854 3854 (((tline->text[1] == '+' || tline->text[1] == '-') (gdb) display tline->text 1: tline->text = 0x0 (gdb) bt #0 0x0000000000426559 in expand_mmac_params (tline=0x7ffff7fc2830, tline@entry=0x7ffff7fc27f0) at modules/preprocs/nasm/nasm-pp.c:3854 #1 0x000000000042b3da in pp_getline () at modules/preprocs/nasm/nasm-pp.c:5070 #2 0x0000000000424956 in nasm_preproc_get_line (preproc=0x6b72a0) at modules/preprocs/nasm/nasm-preproc.c:195 #3 0x0000000000423a7a in nasm_parser_parse (parser_nasm=parser_nasm@entry=0x7fffffffdd10) at modules/parsers/nasm/nasm-parse.c:218 #4 0x00000000004205fc in nasm_do_parse (object=0x6b5ed0, pp=<optimized out>, save_input=0, linemap=<optimized out>, errwarns=0x6b5a00, tasm=<optimized out>) at modules/parsers/nasm/nasm-parser.c:66 #5 0x0000000000402a21 in do_assemble () at frontends/yasm/yasm.c:519 #6 main (argc=<optimized out>, argv=<optimized out>) at frontends/yasm/yasm.c:749 ``` The bug code is listed below. ```c if (tline->type == TOK_PREPROC_ID && (((tline->text[1] == '+' || tline->text[1] == '-') && tline->text[2]) || tline->text[1] == '%' || (tline->text[1] >= '0' && tline->text[1] <= '9'))) ``` ### Error Two: yasm-1.3 has a null pointer dereference in expand_smacro in nasm/nasm-pp.c for insufficient input. ``` cs@ubuntu:~/poc2$ yasm -f bin poc2 -o 1.out Segmentation fault (core dumped) ``` ``` cs@ubuntu:~/poc$ gdb --args yasm -f bin poc2 -o 1.out GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from yasm...done. (gdb) r Starting program: /usr/local/bin/yasm -f bin poc2 -o 1.out Program received signal SIGSEGV, Segmentation fault. 0x00000000004272d4 in expand_smacro (tline=0x7ffff7fc1710, tline@entry=0x7ffff7fbedf0) at modules/preprocs/nasm/nasm-pp.c:4377 4377 tline->mac->in_progress = FALSE; (gdb) display tline->mac 1: tline->mac = (SMacro *) 0x0 (gdb) bt #0 0x00000000004272d4 in expand_smacro (tline=0x7ffff7fc1710, tline@entry=0x7ffff7fbedf0) at modules/preprocs/nasm/nasm-pp.c:4377 #1 0x000000000042b748 in pp_getline () at modules/preprocs/nasm/nasm-pp.c:5119 #2 0x0000000000424956 in nasm_preproc_get_line (preproc=0x6b72a0) at modules/preprocs/nasm/nasm-preproc.c:195 #3 0x0000000000423a7a in nasm_parser_parse (parser_nasm=parser_nasm@entry=0x7fffffffdd10) at modules/parsers/nasm/nasm-parse.c:218 #4 0x00000000004205fc in nasm_do_parse (object=0x6b5ed0, pp=<optimized out>, save_input=0, linemap=<optimized out>, errwarns=0x6b5a00, tasm=<optimized out>) at modules/parsers/nasm/nasm-parser.c:66 #5 0x0000000000402a21 in do_assemble () at frontends/yasm/yasm.c:519 #6 main (argc=<optimized out>, argv=<optimized out>) at frontends/yasm/yasm.c:749 ``` The bug code is listed below. ```c if (tline->type == TOK_SMAC_END) { tline->mac->in_progress = FALSE; tline = delete_Token(tline); } ``` ### Error Three yasm-1.3 has a null pointer dereference or heap buffer over-read in do_directive in nasm/nasm-pp.c for insufficient input. ``` cs@ubuntu:~/poc3$ yasm -f bin poc3 -o 1.out Segmentation fault (core dumped) ``` ``` cs@ubuntu:~/poc$ gdb --args yasm -f bin poc3 -o 1.out GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from yasm...done. (gdb) r Starting program: /usr/local/bin/yasm -f bin poc3 -o 1.out Program received signal SIGSEGV, Segmentation fault. 0x0000000000427608 in do_directive (tline=0x7ffff7fc0530, tline@entry=0x7ffff7fc0550) at modules/preprocs/nasm/nasm-pp.c:2349 2349 (tline->text[1] == '%' || tline->text[1] == '$' (gdb) display tline->text 1: tline->text = 0x0 (gdb) bt #0 0x0000000000427608 in do_directive (tline=0x7ffff7fc0530, tline@entry=0x7ffff7fc0550) at modules/preprocs/nasm/nasm-pp.c:2349 #1 0x000000000042b124 in pp_getline () at modules/preprocs/nasm/nasm-pp.c:5075 #2 0x0000000000424956 in nasm_preproc_get_line (preproc=0x6b72a0) at modules/preprocs/nasm/nasm-preproc.c:195 #3 0x0000000000423a7a in nasm_parser_parse (parser_nasm=parser_nasm@entry=0x7fffffffdd10) at modules/parsers/nasm/nasm-parse.c:218 #4 0x00000000004205fc in nasm_do_parse (object=0x6b5ed0, pp=<optimized out>, save_input=0, linemap=<optimized out>, errwarns=0x6b5a00, tasm=<optimized out>) at modules/parsers/nasm/nasm-parser.c:66 #5 0x0000000000402a21 in do_assemble () at frontends/yasm/yasm.c:519 #6 main (argc=<optimized out>, argv=<optimized out>) at frontends/yasm/yasm.c:749 ``` The bug code is listed below. ```c if (!tok_type_(tline, TOK_PREPROC_ID) || (tline->text[1] == '%' || tline->text[1] == '$' || tline->text[1] == '!')) return NO_DIRECTIVE_FOUND; ```
yasm-1.3 has some errors leading to Segmentation fault
https://api.github.com/repos/yasm/yasm/issues/142/comments
0
2019-12-20T03:14:52Z
2019-12-20T03:14:52Z
https://github.com/yasm/yasm/issues/142
540,723,091
142