【问题标题】:Assembly x86 (32-bit), call to NR_creat (8) Corrupts Filename Storage汇编 x86(32 位),调用 NR_creat (8) 损坏文件名存储
【发布时间】:2014-10-10 09:03:02
【问题描述】:

组装 x86(32 位),调用 NR_creat (8) 损坏文件名存储

所有,我已经竭尽全力试图确定我为文件名保留的存储空间是如何被调用文件 creat (NR_creat 8) 损坏的。汇编器是 nasm,代码是 32 位编译并在 x86_64 盒子上运行。该例程是一段简单的代码,它从程序参数argv[1] 中获取文件名,然后使用该名称创建一个八进制权限为 0644 的文件。该文件被写入,然后程序退出。文件操作有效,问题是我在调用文件creat时丢失了存储在fnbuf中的文件名。

名为fnbuf 的保留存储为32 字节,并在简单的mov [fnbuf], ebx 操作中填充argv[1]。 fnbuf 中的信息在创建文件之前是正常的,此后,fnbuf 中的信息已损坏并且地址已更改。 (所有其他存储的信息都很好)。为了保留文件名,我最终将它推入堆栈(在文件创建后工作正常)我不明白为什么fnbuf 中的信息已损坏并需要帮助。

相关代码如下以及简要的gdb输出(完整代码在最后)。

section    .data
    buflen equ 32

section .bss
    fd_out  resb 1
    fd_in   resb 1
    fnbuf   resb buflen

section    .text

        global  _start
_start:                         ; linker entry point

        ; get the file_name from stdin (argv[1])
        add     esp, 8          ; skip over argc and argv[0] on stack (2 ptr = +8)
        pop     ebx             ; pop argv[1] to ebx
        test    ebx, ebx        ; test if null, jump
        jz      noarg           ; (if pop to ecx, use jecxz - no test required)
        mov     [fnbuf], ebx    ; save the filename in fnbuf (FIXME)
        push    ebx             ; save on stack since fnbuf is getting whacked

        ; output fnbuf to stdout (fnbuf is fine here)
        mov     edi, [fnbuf]    ; load string in edi for length calc & output
        call    strprn          ; calc length and output to stdout
        call    newln           ; output newline to stdout

        ; create the file  (fnbuf is corrupted by this call)
        mov     eax, 8          ; system call number (sys_creat)
        mov     ebx, [fnbuf]    ; set ebx to filename (fine here)
        mov     ecx, 0420       ; 644 octal -rw-r--r--
        int     0x80            ; call kernel
        jc      errcf           ; if carry flag non-zero, jmp errcf
        mov     [fd_out], eax   ; save file descriptor in fd_out

        ; write msg to file
        mov     edi, msg        ; msg address to edi for length
        call    strsz           ; calc length of message to write (ret in edx)
        mov     eax, 4          ; system call number (sys_write)
        mov     ebx, [fd_out]   ; file descriptor
        mov     ecx, msg        ; message to write
        int     0x80            ; call kernel

代码使用以下内容构建并提供以下输出,使用[fnbuf]在file creat调用之前将文件名写入stdout,但之后必须从堆栈中弹出保存的argv[1]以输出file creat 之后的文件名。 [fnbuf] 的使用也很好:

nasm -f elf -o ./obj/filecwr_32.o filecwr_32.asm -g
ld -m elf_i386 -o ./bin/filecwr_32 ./obj/filecwr_32.o

$ ./bin/filecwr_32 newfile.txt
newfile.txt
File write complete.
newfile.txt

$ cat newfile.txt
To whom it may concern, this information was written to the file

使用gdb 单步执行程序显示在内核调用file creat 时发生损坏:

gdb ./bin/filecwr_32
(gdb) set args newfile.txt
(gdb) break 1
Breakpoint 1 at 0x8048080: file filecwr_32.asm, line 1.
(gdb) run
(gdb) watch fnbuf
Hardware watchpoint 2: fnbuf
(gdb) step
Single stepping until exit from function strsz,
which has no line number information.
0x08048095 in strprn ()
(gdb)
Single stepping until exit from function strprn,
which has no line number information.
newfile.txt0x080480f2 in _start ()
(gdb) x/s fnbuf
0xffffd2fd:     "newfile.txt"
(gdb) step
...
Hardware watchpoint 2: fnbuf

Old value = -11523
New value = -11776
0x08048120 in _start ()
(gdb) x/s fnbuf
0xffffd200:     "\376\336\377\377\023\337\377\377\036\337\377\377<\337\377\377\227\337\377\377"
...
[Inferior 1 (process 30000) exited normally]
(gdb) quit

查看上面的gdb 输出,fnbuf 报告的地址发生了变化?它最初位于0xffffd2fd,但随后在0xffffd200 报告——在堆栈的下方大约253 个字节。这令人困惑,我被困在哪里。几乎就像其中一个段地址是移位器一样,但是我希望其余的信息也会被破坏。我的另一个想法是,不知何故 fnbuf 并没有明确表示为 NUL-terminated。我已将其设置为 NUL 并且问题仍然存在。除此之外,除了 x86_64 问题上的流浪 x86 执行之外,我想不出其他任何东西,但这似乎有点牵强。

完整的代码清单:

section    .data
    msg db 'To whom it may concern, this information was written to the file', 0xa, 0
    msg_done db 'File write complete.', 0xa, 0
    msg_noarg db 'No argument available for filename.', 0xa, 0
    msg_create_fail db 'File create failed.', 0xa, 0

    buflen equ 32
    nwln db 0xa

section .bss
    fd_out  resb 1
    fd_in   resb 1
    flen    resb 1
    fnbuf   resb buflen

section    .text
            global  _start

    ; szstr computes the length of a string.
    ; edi - string address
    ; edx - contains string length (returned)
    strsz:
            xor     ecx, ecx        ; zero rcx
            not     ecx             ; set rcx = -1 (uses bitwise id: ~x = -x-1)
            xor     al,al           ; zero the al register (initialize to NUL)
            cld                     ; clear the direction flag
            repnz   scasb           ; get the string length (dec ecx through NUL)
            not     ecx             ; rev all bits of negative -> absolute value
            dec     ecx             ; -1 to skip the null-term, ecx contains length
            mov     edx, ecx        ; size returned in edx, ready to call write
            ret

    ; strprn writes a string to the file descriptor.
    ; edi - string address
    ; edx - contains string length
    strprn:
            push    edi             ; push string address onto stack
            call    strsz           ; call strsz to get length
            pop     ecx             ; pop string to ecx esi (source index)
            mov     eax, 0x4        ; write/stdout number in eax (sys_write 4)
            mov     ebx, 0x1        ; set destination index to ebx (stdout 1)
            int     0x80            ; call kernel
            ret

    ; newln writes a newline to the file descriptor.
    newln:
            mov     ecx, nwln       ; set string index in ecx
            mov     ebx, 0x1        ; set destination index to (stdout 1)
            mov     edx, 0x1        ; set length of string in edx
            mov     eax, 0x4        ; mov write syscall number (4) to eax
            int     0x80            ; call kernel
            ret

    ; error function for no argument
    noarg:
            mov     edi, msg_noarg  ; error msg to edi for length calc
            call    strprn          ; calc length and output to stdout
            jmp     exit

    ; error on fail to create file
    errcf:
            mov     edi, msg_create_fail ; error msg to edi for length calc
            call    strprn          ; calc length and output to stdout
            jmp     exit

    _start:                         ; linker entry point

            ; get the file_name from stdin (argv[1])
            add     esp, 8          ; skip over argc and argv[0] on stack (2 ptr = +8)
            pop     ebx             ; pop argv[1] to ebx
            test    ebx, ebx        ; test if null, jump
            jz      noarg           ; (if pop to ecx, use jecxz - no test required)
            mov     [fnbuf], ebx    ; save the filename in fnbuf (FIXME)
            push    ebx             ; save on stack since fnbuf is getting whacked

            ; output fnbuf to stdout (fnbuf is fine here)
            mov     edi, [fnbuf]    ; load string in edi for length calc & output
            call    strprn          ; calc length and output to stdout
            call    newln           ; output newline to stdout

            ; create the file  (fnbuf is corrupted by this call)
            mov     eax, 8          ; system call number (sys_creat)
            mov     ebx, [fnbuf]    ; set ebx to filename (fine here)
            mov     ecx, 0420       ; 644 octal -rw-r--r--
            int     0x80            ; call kernel
            jc      errcf           ; if carry flag non-zero, jmp errcf
            mov     [fd_out], eax   ; save file descriptor in fd_out

            ; write msg to file
            mov     edi, msg        ; msg address to edi for length
            call    strsz           ; calc length of message to write (ret in edx)
            mov     eax, 4          ; system call number (sys_write)
            mov     ebx, [fd_out]   ; file descriptor
            mov     ecx, msg        ; message to write
            int     0x80            ; call kernel

            ; close the file
            mov     eax, 6          ; set eax sys_close
            mov     ebx, [fd_out]   ; file descriptor in ebx 
            int     0x80

            ; print write done to stdout
            mov     edi, msg_done   ; msg_done in ecx
            call    strprn          ; calc length and output to stdout

            ; print file name to stdout
            ; mov     edi, [fnbuf]    ; fnbuf corrupted? Segment smashed?
            pop     edi             ; pop original filename from stack
            push    edi             ; save another copy since fnbuf is messed up
            call    strprn          ; calc length and output to stdout
            call    newln           ; output newline
            jmp     exit

    exit:
            xor     ebx, ebx        ; set exit code to 0
            mov     eax,1           ; system call number (sys_exit)
            int     0x80            ; call kernel

我不知道是什么导致了fnbuf 的损坏。此外,在其他一切似乎都按预期工作的情况下,可能仅影响该地址的因素。任何帮助将不胜感激。

【问题讨论】:

    标签: linux assembly nasm


    【解决方案1】:

    首先,你弄乱了一个指针和一个缓冲区:

    fnbuf   resb buflen
    

    分配您可能希望用作缓冲区的“buflen”字节数(32), 但是

    mov     [fnbuf], ebx    ; save the filename in fnbuf (FIXME)
    

    将包含在ebx 中的地址(指针)存储到fnbuf 的前四个字节中 - 它不会将文件名本身或其他任何内容复制到缓冲区,只是指向文件名的指针。转储你的.bss 内存区域之后会给出这个输出(注意fd_out 是你.bss 区域的第一个地址):

    (gdb) x/32 0x80491ec
    0x80491ec <fd_out>: 0x00    0x00    0x00    0xac    0xd2    0xff    0xff    0x00
                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                                                 Pointer retrieved from EBX
    

    但是,真正的问题是您将文件描述符存储到 fd_out 的位置:

    mov     [fd_out], eax   ; save file descriptor in fd_out
    

    这会将四个 (!!) 字节从 eax 写入从 fd_out 开始的内存。转储相同的内存 结果是

                                              Destroyed!
    (gdb) x/32 0x80491ec                        ****
    0x80491ec <fd_out>: 0x03    0x00    0x00    0x00    0xd2    0xff    0xff    0x00
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                         Four bytes written by mov
    

    如您所见,这个 mov 破坏了指针的第一个字节 - 它被设置为 0x00 从而导致 在您观察到的修改后的值中。

    【讨论】:

    • 安德烈亚斯,谢谢。所以为了在fnbuf中存储argv[1],我需要在si中使用rep movsb和argv[1],在di中使用fnbuf?
    • 基本上是的 - 不要忘记正确设置 ECX 和 direction flag
    猜你喜欢
    • 2011-11-04
    • 1970-01-01
    • 2017-10-20
    • 2015-05-31
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2021-07-29
    相关资源
    最近更新 更多