[Nasm-bugs] [Bug 3392849] New: Stack overflow in nasm (function ieee_unqualified_name)

[noreply-nasm at dev.nasm.us]

https://bugzilla.nasm.us/show_bug.cgi?id=3392849

            Bug ID: 3392849
           Summary: Stack overflow in nasm (function
                    ieee_unqualified_name)
           Product: NASM
           Version: 2.17 (development)
          Hardware: All
                OS: Linux
            Status: OPEN
          Severity: normal
          Priority: Medium
         Component: Assembler
          Assignee: nobody at nasm.us
          Reporter: youngseok.main at gmail.com
                CC: chang.seok.bae at intel.com, gorcunov at gmail.com,
                    hpa at zytor.com, nasm-bugs at nasm.us
     Obtained from: Built from git using configure

Created attachment 411873
  --> https://bugzilla.nasm.us/attachment.cgi?id=411873&action=edit
poc_file

Hello,

Our fuzzer found a stack overflow bug in nasm.

Command Input:
nasm poc_file -fieee

poc_file is attached.

Command Output:
poc_file:1: warning: label alone on a line without a colon might be in error
[-w+label-orphan]
poc_file:3: warning: label alone on a line without a colon might be in error
[-w+label-orphan]

Sanitizer Dump:
==32504==ERROR: AddressSanitizer: stack-buffer-overflow on address
0x7fffffffdae0 at pc 0x7ffff6e7e3a6 bp 0x7fffffffd930 sp 0x7fffffffd0d8
WRITE of size 7540 at 0x7fffffffdae0 thread T0
    #0 0x7ffff6e7e3a5  (/usr/lib/x86_64-linux-gnu/libasan.so.4+0x663a5)
    #1 0x5555557239eb in ieee_unqualified_name output/outieee.c:1282
    #2 0x555555720e74 in ieee_write_file output/outieee.c:956
    #3 0x55555571cc12 in ieee_cleanup output/outieee.c:231
    #4 0x555555681f92 in main asm/nasm.c:719
    #5 0x7ffff6a48c86 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x21c86)
    #6 0x55555567f699 in _start
(/home/youngseok/latest-subjects/nasm/nasm+0x12b699)

Environment:
OS: Ubuntu 18.04
gcc: 7.5.0
nasm: 2.17rc0 (Git master branch, a916e4127b2eaa3bf40bddf3de9b0ceefc0d98a)

Note that we built nasm with sanitizers.

Any comments related to the crash are welcome. Since we are developing a new
fuzzing technique, it would be very helpful for our work.

Thank you.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are watching all bug changes.