• Title/Summary/Keyword: Taint analysis

Search Result 13, Processing Time 0.025 seconds

A Study on MS Crash Analyzer (MS 크래시 분석도구에 관한 연구)

  • Noh, Myoung Sun;Na, Jong Bae;Jung, Gwang Un;Ryou, Jae Cheol;Noh, Bong Nam
    • KIPS Transactions on Computer and Communication Systems
    • /
    • v.2 no.9
    • /
    • pp.399-404
    • /
    • 2013
  • MSEC(Microsoft Security Engineering Center) performed fuzz testing Windows Vista with 350 million test cases for 14 months before launching it. They analyzed crashes resulted from the testing and developed crash analyzer !exploitable based on the data used to determine exploitability. In this paper, we describe how MS crash analyzer determines exploitability of crashes. Besides, we suggest an improvement to overcome the limitations found in the MS crash analyzer during the analysis.

Graph based Binary Code Execution Path Exploration Platform for Dynamic Symbolic Execution (동적 기호 실행을 이용한 그래프 기반 바이너리 코드 실행 경로 탐색 플랫폼)

  • Kang, Byeongho;Im, Eul Gyu
    • Journal of the Korea Institute of Information Security & Cryptology
    • /
    • v.24 no.3
    • /
    • pp.437-444
    • /
    • 2014
  • In this paper, we introduce a Graph based Binary Code Execution Path Exploration Platform. In the graph, a node is defined as a conditional branch instruction, and an edge is defined as the other instructions. We implemented prototype of the proposed method and works well on real binary code. Experimental results show proposed method correctly explores execution path of target binary code. We expect our method can help Software Assurance, Secure Programming, and Malware Analysis more correct and efficient.

Enhancement of Accuracy of Exploitability Analysis Tools for Crashes (크래시의 위험도에 대한 분석 도구의 정교성 향상)

  • Jeon, Hyeon-gu;Eom, Ki-Jin;Mok, Seong-Kyun;Cho, Eun-Sun
    • KIISE Transactions on Computing Practices
    • /
    • v.22 no.4
    • /
    • pp.178-183
    • /
    • 2016
  • To enhance the reliability of programs, developers use fuzzing tools in test processes to identify vulnerabilities so that they can be fixed ahead of time. In this case, the developers consider the security-related vulnerabilities to be the most critical ones that should be urgently fixed to avoid possible exploitation by attackers. However, developers without much experience of analysis of vulnerabilities usually rely on tools to pick out the security-related crashes from the normal crashes. In this paper, we suggest a static analysis-based tool to help developers to make their programs more reliable by identifying security-related crashes among them. This paper includes experimental results, and compares them to the results from MSEC !exploitable for the same sets of crashes.