Skip to content
This repository was archived by the owner on Sep 17, 2018. It is now read-only.
This repository was archived by the owner on Sep 17, 2018. It is now read-only.

Access violation near NULL on destination operand #4

Closed
@kongwenbin

Description

@kongwenbin

I have discovered several malformed cue files that would cause bchunk to run into segmentation fault. With the help of gdb exploitable, it can be determined that there was an access violation near NULL on the destination operand.

The following is a full output:

Program received signal SIGSEGV, Segmentation fault.
0x08135475 in main (argc=<optimized out>, argv=<optimized out>) at bchunk.c:488
488                track->startsect = time2frames(t);
(gdb) exploitable
__main__:99: UserWarning: GDB v7.11 may not support required Python API
Description: Access violation near NULL on destination operand
Short description: DestAvNearNull (15/22)
Hash: a9a47a861a48dcf377b1bb07b521fa30.a9a47a861a48dcf377b1bb07b521fa30
Exploitability Classification: PROBABLY_EXPLOITABLE
Explanation: The target crashed on an access violation at an address matching the destination operand of the instruction. This likely indicates a write access violation, which means the attacker may control write address and/or value. However, it there is a chance it could be a NULL dereference.
Other tags: AccessViolation (21/22)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions