DOCSLIB.ORG

HLASM V1R6 Toolkit Feature User's Guide CMS Files Used by Superc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

High Level Assembler for z/OS & z/VM & z/VSE IBM Toolkit Feature User's Guide Version 1 Release 6 GC26-8710-12 High Level Assembler for z/OS & z/VM & z/VSE IBM Toolkit Feature User's Guide Version 1 Release 6 GC26-8710-12 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page 331. This edition applies to IBM High Level Assembler for z/OS & z/VM & z/VSE Toolkit Feature, Release 6, Program Number 5696-234 and to any subsequent releases until otherwise indicated in new editions. Make sure that you are using the correct edition for the level of the product. Order publications through your IBM representative or the IBM branch office serving your locality. IBM welcomes your comments. For information on how to send comments, see “How to send your comments to IBM” on page xv. © Copyright IBM Corporation 1992, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures .............. vii The CASE macro set ........... 32 The SELECT macro set .......... 35 Tables ............... ix Chapter 3. Using the disassembler... 39 About this document ......... xi Invoking the disassembler ......... 40 Invoking the disassembler on z/OS ..... 40 Who should use this document ........ xi Invoking the disassembler on CMS ..... 42 Syntax notation ............. xi Invoking the disassembler on z/VSE ..... 44 Control statements ............ 45 How to send your comments to IBM .. xv Module-CSECT statement (required) ..... 46 If you have a technical problem ....... xv DATA-only statement (optional) ...... 47 INSTR-only statement (optional) ...... 47 Summary of changes ........ xvii DS-area statement (optional)........ 47 DSECT definitions (optional) ....... 48 Chapter 1. Introducing the Toolkit ULABL statements ........... 48 Feature ............... 1 USING statements ........... 48 COPY statement (optional) ........ 49 Toolkit Feature components ......... 2 Comment statement (optional) ....... 49 Toolkit Feature structured programming macros . 2 Disassembling a module for the first time .... 49 Toolkit Feature Disassembler ........ 2 Output description ............ 50 Toolkit Feature Program Understanding Tool .. 3 SYSPUNCH (SYSPCH for z/VSE) content ... 50 Toolkit Feature Cross-Reference Facility .... 4 SYSPRINT (SYSLST for z/VSE) content .... 51 Toolkit Feature Interactive Debug Facility.... 5 Disassembler CMS messages ........ 52 Enhanced SuperC............ 6 Disassembler messages .......... 54 Potential uses for the Toolkit Feature ...... 6 Recovery and reconstruction ........ 7 Analysis and understanding ........ 8 Chapter 4. Using the Program Modification and testing ......... 8 Understanding Tool ......... 59 Summary .............. 9 Introducing ASMPUT ........... 59 More about nodes ........... 60 Chapter 2. Using structured Getting started ............ 61 programming macros ........ 11 Working with ADATA files ......... 64 Opening an ADATA file ......... 64 Accessing the macros ........... 12 Opening and closing the control flow graph The ASMMREL macro ........... 13 window .............. 65 The IF macro set............. 13 Viewing source code .......... 65 IF macro option A ........... 14 Viewing ADATA file information ...... 70 IF macro option B ........... 15 Viewing Job Id information ........ 72 IF macro option C ........... 16 Viewing HLASM files information...... 72 IF macro option D ........... 17 Viewing options information ....... 72 IF macros with Boolean operators ...... 17 Viewing statistics information ....... 73 The ELSEIF macro ........... 19 Viewing libraries information ....... 73 The DO macro set ............ 20 Removing (closing) a file ......... 73 The DO indexing group ......... 21 Working with the control flow graph ...... 73 DO loop terminator generation ....... 22 Expanding and collapsing layers ...... 74 Simple DO ............. 22 Adding and removing context ....... 80 Infinite loop ............. 22 Refreshing and redoing ......... 81 Branching to the ENDDO......... 23 Hiding and showing return arcs ...... 82 Leaving a nested DO .......... 24 Marking and unmarking nodes ....... 83 Explicit specification .......... 25 Opening and closing the Overview window .. 84 Counting .............. 25 Zooming .............. 85 Backward indexing ........... 26 Scrolling .............. 88 Forward indexing ........... 27 The interaction between source code and the Register initialization .......... 27 control flow graph ........... 89 The UNTIL and WHILE keywords ..... 28 ASMPUT windows and window areas ..... 91 Looping with DOEXIT and EXITIF ..... 29 Main window ............ 91 The SEARCH macro set .......... 30 © Copyright IBM Corp. 1992, 2017 iii Control Flow Graph window ....... 99 Invoking the comparison on CMS using Control Flow Graph window menu options and command line input .......... 198 toolbar icons ............ 101 Invoking the comparison on z/VSE ..... 205 Overview window .......... 106 Invoking the SuperC search ........ 211 Restrictions .............. 106 Invoking the search on z/OS ....... 212 Using online help ............ 107 Invoking the search on CMS using menu input 213 Using topic help ........... 107 Invoking the search on CMS using command Using what's this help ......... 108 line input.............. 220 ASMPUT messages ........... 108 Invoking the search on z/VSE....... 227 Process options ............. 231 Chapter 5. Using the Cross-Reference Process statements............ 243 Facility .............. 115 Change listing value .......... 245 Change text ............. 245 Invoking the Cross-Reference Facility ..... 116 Comment lines ............ 247 Invoking ASMXREF on z/OS ....... 117 Compare byte offsets .......... 247 Invoking ASMXREF on CMS ....... 125 Compare (search) columns ........ 248 Invoking ASMXREF on z/VSE ...... 131 Compare lines ............ 249 ASMXREF Control Statements........ 136 Compare sections ........... 251 *................. 136 DD-MVS alternate DD names ....... 252 Library .............. 136 DD-VSE DLBL/TLBL definitions ...... 253 Include .............. 137 Define column headings......... 256 Exclude .............. 138 Do not process lines .......... 258 Parm ............... 138 Exclude data ............ 259 Report............... 139 Focus on data ............ 260 ASMXREF Token Statement ........ 139 Line count ............. 261 Token ............... 140 List columns ............ 261 Scanning rules for ASMXREF ....... 142 List previous-search-following value..... 262 ASMXREF Options ........... 143 Revision code reference ......... 262 ASMXREF XRFLANG Statements ...... 143 Search strings in the input file....... 263 Default token segment ......... 144 Select files from a list of files (CMS) ..... 264 Language segment .......... 145 Select members or files (CMS) ....... 265 ASMXREP Options ........... 145 Select members (z/VSE) ......... 266 Understanding the reports ......... 146 Select PDS members (z/OS) ....... 268 Languages supported by reports ...... 146 Statements file listing control ....... 269 Control flow (CF) report......... 147 Title alternative listing ......... 269 Lines Of Code (LOC) report ....... 150 Work size ............. 270 The LOOC report ........... 155 Year aging ............. 270 Macro Where Used (MWU) report ..... 157 Date definitions ........... 271 Spreadsheet Oriented Report (SOR) ..... 158 Global date ............. 274 Symbol Where Used (SWU) report ..... 160 CMS command line option directives ..... 274 Token Where Used (TWU) report...... 163 CMS command line statement option directives 275 Tagged Source Program (TSP) ....... 164 Understanding the listings ......... 277 ASMXREF Messages ........... 168 General listing format ......... 277 Message list ............. 169 How to view the listing output ...... 277 ASMXREF User Abends .......... 179 The comparison listing ......... 278 The search listing ........... 290 Chapter 6. Using Enhanced SuperC 181 Update files .............. 298 The SuperC comparison .......... 181 Revision file ............. 299 The SuperC search ........... 182 Revision file (2)............ 300 SuperC features for date comparisons ..... 183 Update CMS sequenced 8 file ....... 301 General applications ........... 183 Update control files .......... 302 How SuperC and search-for filter input file lines 184 Update long control .......... 305 How SuperC corrects false matches ...... 185 Update MVS sequenced 8 file ....... 306 How SuperC partitions and processes large files 186 Update prefixed delta lines ........ 307 Comparing load modules ......... 186 Update sequenced 0 file ......... 307 Comparing CSECTs ........... 187 Update summary only files........ 308 Invoking the SuperC comparison ....... 187 CMS file selection list........... 311 Invoking the comparison on z/OS ..... 187 Getting to the selection list menus ..... 312 Invoking the comparison on CMS using menu How SuperC pairs CMS files and members ... 317 input ............... 190 Pairing Files ............. 317 Pairing members ........... 318 iv HLASM V1R6 Toolkit Feature User's Guide CMS files used by SuperC ......... 318 Bibliography............ 333 Reasons for differing comparison results .... 319 Return codes ............. 320 Glossary ............. 335 SuperC messages ............ 321 Index ............... 343 Notices .............. 331 Trademarks .............. 332 Contents v vi HLASM V1R6 Toolkit Feature User's Guide Figures 1. Typical phases for Toolkit Feature usage ... 6 46. Sample LOC per Class section
Recommended publications
  • Fill Your Boots: Enhanced Embedded Bootloader Exploits Via Fault Injection and Binary Analysis

    Fill Your Boots: Enhanced Embedded Bootloader Exploits Via Fault Injection and Binary Analysis

    IACR Transactions on Cryptographic Hardware and Embedded Systems ISSN 2569-2925, Vol. 2021, No. 1, pp. 56–81. DOI:10.46586/tches.v2021.i1.56-81 Fill your Boots: Enhanced Embedded Bootloader Exploits via Fault Injection and Binary Analysis Jan Van den Herrewegen1, David Oswald1, Flavio D. Garcia1 and Qais Temeiza2 1 School of Computer Science, University of Birmingham, UK, {jxv572,d.f.oswald,f.garcia}@cs.bham.ac.uk 2 Independent Researcher, [email protected] Abstract. The bootloader of an embedded microcontroller is responsible for guarding the device’s internal (flash) memory, enforcing read/write protection mechanisms. Fault injection techniques such as voltage or clock glitching have been proven successful in bypassing such protection for specific microcontrollers, but this often requires expensive equipment and/or exhaustive search of the fault parameters. When multiple glitches are required (e.g., when countermeasures are in place) this search becomes of exponential complexity and thus infeasible. Another challenge which makes embedded bootloaders notoriously hard to analyse is their lack of debugging capabilities. This paper proposes a grey-box approach that leverages binary analysis and advanced software exploitation techniques combined with voltage glitching to develop a powerful attack methodology against embedded bootloaders. We showcase our techniques with three real-world microcontrollers as case studies: 1) we combine static and on-chip dynamic analysis to enable a Return-Oriented Programming exploit on the bootloader of the NXP LPC microcontrollers; 2) we leverage on-chip dynamic analysis on the bootloader of the popular STM8 microcontrollers to constrain the glitch parameter search, achieving the first fully-documented multi-glitch attack on a real-world target; 3) we apply symbolic execution to precisely aim voltage glitches at target instructions based on the execution path in the bootloader of the Renesas 78K0 automotive microcontroller.
  • Radare2 Book

    Radare2 Book

    Table of Contents introduction 1.1 Introduction 1.2 History 1.2.1 Overview 1.2.2 Getting radare2 1.2.3 Compilation and Portability 1.2.4 Compilation on Windows 1.2.5 Command-line Flags 1.2.6 Basic Usage 1.2.7 Command Format 1.2.8 Expressions 1.2.9 Rax2 1.2.10 Basic Debugger Session 1.2.11 Contributing to radare2 1.2.12 Configuration 1.3 Colors 1.3.1 Common Configuration Variables 1.3.2 Basic Commands 1.4 Seeking 1.4.1 Block Size 1.4.2 Sections 1.4.3 Mapping Files 1.4.4 Print Modes 1.4.5 Flags 1.4.6 Write 1.4.7 Zoom 1.4.8 Yank/Paste 1.4.9 Comparing Bytes 1.4.10 Visual mode 1.5 Visual Disassembly 1.5.1 2 Searching bytes 1.6 Basic Searches 1.6.1 Configurating the Search 1.6.2 Pattern Search 1.6.3 Automation 1.6.4 Backward Search 1.6.5 Search in Assembly 1.6.6 Searching for AES Keys 1.6.7 Disassembling 1.7 Adding Metadata 1.7.1 ESIL 1.7.2 Scripting 1.8 Loops 1.8.1 Macros 1.8.2 R2pipe 1.8.3 Rabin2 1.9 File Identification 1.9.1 Entrypoint 1.9.2 Imports 1.9.3 Symbols (exports) 1.9.4 Libraries 1.9.5 Strings 1.9.6 Program Sections 1.9.7 Radiff2 1.10 Binary Diffing 1.10.1 Rasm2 1.11 Assemble 1.11.1 Disassemble 1.11.2 Ragg2 1.12 Analysis 1.13 Code Analysis 1.13.1 Rahash2 1.14 Rahash Tool 1.14.1 Debugger 1.15 3 Getting Started 1.15.1 Registers 1.15.2 Remote Access Capabilities 1.16 Remoting Capabilities 1.16.1 Plugins 1.17 Plugins 1.17.1 Crackmes 1.18 IOLI 1.18.1 IOLI 0x00 1.18.1.1 IOLI 0x01 1.18.1.2 Avatao 1.18.2 R3v3rs3 4 1.18.2.1 .intro 1.18.2.1.1 .radare2 1.18.2.1.2 .first_steps 1.18.2.1.3 .main 1.18.2.1.4 .vmloop 1.18.2.1.5 .instructionset 1.18.2.1.6
  • Reverse Software Engineering As a Project-Based Learning Tool

    Reverse Software Engineering As a Project-Based Learning Tool

    Paper ID #33764 Reverse Software Engineering as a Project-Based Learning Tool Ms. Cynthia C. Fry, Baylor University CYNTHIA C. FRY is currently a Senior Lecturer of Computer Science at Baylor University. She worked at NASA’s Marshall Space Flight Center as a Senior Project Engineer, a Crew Training Manager, and the Science Operations Director for STS-46. She was an Engineering Duty Officer in the U.S. Navy (IRR), and worked with the Naval Maritime Intelligence Center as a Scientific/Technical Intelligence Analyst. She was the owner and chief systems engineer for Systems Engineering Services (SES), a computer systems design, development, and consultation firm. She joined the faculty of the School of Engineering and Computer Science at Baylor University in 1997, where she teaches a variety of engineering and computer science classes, she is the Faculty Advisor for the Women in Computer Science (WiCS), the Director of the Computer Science Fellows program, and is a KEEN Fellow. She has authored and co- authored over fifty peer-reviewed papers. Mr. Zachary Michael Steudel Zachary Steudel is a 2021 graduate of Baylor University’s computer science department. In his time at Baylor, he worked as a Teaching Assistant under Ms. Cynthia C. Fry. As part of the Teaching Assistant role, Zachary designed and created the group project for the Computer Systems course. Zachary Steudel worked as a Software Developer Intern at Amazon in the Summer of 2019, a Software Engineer Intern at Microsoft in the Summer of 2020, and begins his full-time career with Amazon in the summer of 2021 as a software engineer.
  • Reassembleable Disassembling

    Reassembleable Disassembling

    Reassembleable Disassembling Shuai Wang, Pei Wang, and Dinghao Wu College of Information Sciences and Technology The Pennsylvania State University fszw175, pxw172, [email protected] Abstract struction level to enforce certain security policies. To ensure program control-flow integrity (CFI, meaning that Reverse engineering has many important applications in program execution is dictated to a predetermined control- computer security, one of which is retrofitting software flow graph) [1,4, 43, 17, 29, 37] without source code, the for safety and security hardening when source code is not original control-flow graph must be recovered from a bi- available. By surveying available commercial and aca- nary executable and the binary must be retrofitted with demic reverse engineering tools, we surprisingly found the CFI enforcement facility embedded [50, 49]. Sym- that no existing tool is able to disassemble executable bolic taint analysis [34] on binaries must recover assem- binaries into assembly code that can be correctly assem- bly code and data faithfully. The defending techniques bled back in a fully automated manner, even for simple against return-oriented programming (ROP) attacks also programs. Actually in many cases, the resulted disas- rely on binary analysis and reconstruction to identify and sembled code is far from a state that an assembler ac- eliminate ROP gadgets [44,9, 47, 22, 39]. cepts, which is hard to fix even by manual effort. This Despite the fact that many security hardening tech- has become a severe obstacle. People have tried to over- niques are highly dependent on reverse engineering, flex- come it by patching or duplicating new code sections for ible and easy-to-use binary manipulation itself remains retrofitting of executables, which is not only inefficient an unsolved problem.
  • A Survey of Reverse Engineering Tools for the 32-Bit Microsoft Windows Environment

    A Survey of Reverse Engineering Tools for the 32-Bit Microsoft Windows Environment

    A Survey of Reverse Engineering Tools for the 32-Bit Microsoft Windows Environment RAYMOND J. CANZANESE, JR., MATTHEW OYER, SPIROS MANCORIDIS, and MOSHE KAM College of Engineering Drexel University, Philadelphia, PA, USA Reverse engineering is defined by Chikosfky and Cross as the process of analyzing a subject system to identify the system's components and their relationships, and to create representations of the system in another form or at a higher level of abstraction. The process of reverse engineering is accomplished using specific tools that, for the 32-bit Microsoft Windows environment, are categorized as hex editors, disassemblers/debuggers, decompilers, or related technologies such as code obfuscators, unpackers, and PE editors. An evaluation of each tool is provided that identifies its domain of applicability and usability. Categories and Subject Descriptors: A.1 [General]: Introductory and Survey; D.2.5 [Software Engineering]: Testing and Debugging General Terms: Security, Documentation Additional Key Words and Phrases: Reverse Engineering, Disassemblers, Debuggers, Decompilers, Code Obfuscators, PE Editors Unpackers, Hex Editors 1. INTRODUCTION 1.1 The Reverse Engineering Process Software engineers are sometimes asked to understand the behavior of a program given that program's binary executable file. If they have access to the appropriate reverse engineering tools, they might choose to adhere to the following process. First, a general disassembler/debugger is used to determine the basic functionality of the program. If disassembly and debugging shows that the binary code has been obfuscated, the next step would be to determine whether the obfuscator used is a common commercial obfuscator or a custom protection scheme. A PE editor would be used to make this determination.
  • Implementing the UCSD PASCAL System on the MODCOMP Computer

    Implementing the UCSD PASCAL System on the MODCOMP Computer

    TDA Progress Report 42-60 September and October 1960 Implementing the UCSD PASCAL System on the MODCOMP Computer T. Wolfe DSN Data Systems Section This article describes the UCSD PASCAL system developed by the University of California, San Diego, now available on the MODCOMP computer. The system includes a Pascal compiler and many useful utility programs. A BASIC compiler and a FORTRAN 77 compiler are also avatkble. There is currently a large amount of software availabie written in UCSD PASCAL, including a data base system, word processing systems and a MODULA compiler. I. Introduction Assembly language subroutines thus produced may also be called from either Pascal or FORTRAN. Currently the assem- The UCSD PASCAL* System is a complete interactive bler has not been modified to produce MODCOMP machine software development system consisting of an operating sys- code. A system library program may be used to build libraries tem, compilers (Pascal, BASIC, FORTRAN 77) two text of useful subroutines and the system linker used to link them editors (screen editor and line-oriented editor), a linker and to user programs. many useful utility programs. The system is written and main- tained in Pascal. The compiler generates code for an idealized processor known as the “pseudo-machine.” The “pseudo- Interpreters currently exist for Z80/8080, PDP 11 /LSI-1 1, code” (p-code) generated by the compiler is interpreted at 6800, 9900 and 6502 computers and are being developed for runtime by a program (known as the interpreter) which emu- other computers. Thus, software could be developed on an lates the pseudo-machine.
  • V850 Series Development Environment Pamphlet

    V850 Series Development Environment Pamphlet

    To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.com April 1st, 2010 Renesas Electronics Corporation Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry. Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
  • X86 Disassembly Exploring the Relationship Between C, X86 Assembly, and Machine Code

    X86 Disassembly Exploring the Relationship Between C, X86 Assembly, and Machine Code

    x86 Disassembly Exploring the relationship between C, x86 Assembly, and Machine Code PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 07 Sep 2013 05:04:59 UTC Contents Articles Wikibooks:Collections Preface 1 X86 Disassembly/Cover 3 X86 Disassembly/Introduction 3 Tools 5 X86 Disassembly/Assemblers and Compilers 5 X86 Disassembly/Disassemblers and Decompilers 10 X86 Disassembly/Disassembly Examples 18 X86 Disassembly/Analysis Tools 19 Platforms 28 X86 Disassembly/Microsoft Windows 28 X86 Disassembly/Windows Executable Files 33 X86 Disassembly/Linux 48 X86 Disassembly/Linux Executable Files 50 Code Patterns 51 X86 Disassembly/The Stack 51 X86 Disassembly/Functions and Stack Frames 53 X86 Disassembly/Functions and Stack Frame Examples 57 X86 Disassembly/Calling Conventions 58 X86 Disassembly/Calling Convention Examples 64 X86 Disassembly/Branches 74 X86 Disassembly/Branch Examples 83 X86 Disassembly/Loops 87 X86 Disassembly/Loop Examples 92 Data Patterns 95 X86 Disassembly/Variables 95 X86 Disassembly/Variable Examples 101 X86 Disassembly/Data Structures 103 X86 Disassembly/Objects and Classes 108 X86 Disassembly/Floating Point Numbers 112 X86 Disassembly/Floating Point Examples 119 Difficulties 121 X86 Disassembly/Code Optimization 121 X86 Disassembly/Optimization Examples 124 X86 Disassembly/Code Obfuscation 132 X86 Disassembly/Debugger Detectors 137 Resources and Licensing 139 X86 Disassembly/Resources 139 X86 Disassembly/Licensing 141 X86 Disassembly/Manual of Style 141 References Article Sources and Contributors 142 Image Sources, Licenses and Contributors 143 Article Licenses License 144 Wikibooks:Collections Preface 1 Wikibooks:Collections Preface This book was created by volunteers at Wikibooks (http:/ / en.
  • Cubesuite+ V1.00.00 Integrated Development Environment User's Manual: V850 Build

    Cubesuite+ V1.00.00 Integrated Development Environment User's Manual: V850 Build

    User’s Manual User’s CubeSuite+ V1.00.00 Integrated Development Environment User’s Manual: V850 Build Target Device V850 Microcontroller All information contained in these materials, including products and product specifications, represents information on the product at the time of publication and is subject to change by Renesas Electronics Corp. without notice. Please review the latest information published by Renesas Electronics Corp. through various means, including the Renesas Electronics Corp. website (http://www.renesas.com). www.renesas.com Rev.1.00 Apr 2011 Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
  • GPU-Disasm: a GPU-Based X86 Disassembler

    GPU-Disasm: a GPU-Based X86 Disassembler

    GPU-Disasm: A GPU-based x86 Disassembler Evangelos Ladakis1, Giorgos Vasiliadis1, Michalis Polychronakis2, Sotiris Ioannidis1, and Georgios Portokalidis3 1 FORTH-ICS, Greece fladakis, gvasil, [email protected] 2 Stony Brook University, USA [email protected] 3 Stevens Institute of Technology, USA [email protected] Abstract. Static binary code analysis and reverse engineering are cru- cial operations for malware analysis, binary-level software protections, debugging, and patching, among many other tasks. Faster binary code analysis tools are necessary for tasks such as analyzing the multitude of new malware samples gathered every day. Binary code disassembly is a core functionality of such tools which has not received enough atten- tion from a performance perspective. In this paper we introduce GPU- Disasm, a GPU-based disassembly framework for x86 code that takes advantage of graphics processors to achieve efficient large-scale analy- sis of binary executables. We describe in detail various optimizations and design decisions for achieving both inter-parallelism, to disassem- ble multiple binaries in parallel, as well as intra-parallelism, to decode multiple instructions of the same binary in parallel. The results of our experimental evaluation in terms of performance and power consumption demonstrate that GPU-Disasm is twice as fast than a CPU disassembler for linear disassembly and 4.4 times faster for exhaustive disassembly, with power consumption comparable to CPU-only implementations. 1 Introduction Code disassemblers are typically used to translate byte code to assembly lan- guage, as a first step in understanding the functionality of binaries when source code is not available. Besides software debugging and reverse engineering, dis- assemblers are widely used by security experts to analyze and understand the behaviour of malicious programs [8,12], or to find software bugs and vulnerabili- ties in closed-source applications.
  • Disassembler Using High Level Processor Models

    Disassembler Using High Level Processor Models

    Disassembler using High Level Pro cessor Mo dels A T h e s i s S u b m i t t e d in P a r t i a l Fu l l l m e n t o f th e Requirem ents fo r t h e D e g r e e o f M a s t e r o f Te c h n o l o g y by Nihal Chand Jain t o t h e Department of Computer Science Engineering Indian Institute of Technology Kanpur Jan Certicate Certied that the work contained in the thesis entitled D i s a s s e m b l e r u s i n g H i g h L e v e l P r o c e s s o r M o d e l s by MrN i h a l C h a n d J a i n has b een carried out under my sup ervision and that this work has not b een submitted elsewhere for a degree Dr Ra jat Mo ona Asso ciate Professor Department of Computer Science Engineering Indian Institute of Technology Kanpur Jan ii Abstract The design of a high p erformance system requires an integrated environment to sim ulate and analyze the p erformance of various design alternatives In this thesis we have develop ed a g e n e r i c disassem b ler for an integrated environment where SimnML acts as the sp ecication language for pro cessor p erformance mo del The SimnML an extension of nML machine description formalism is a simple elegant and p owerful language to mo del machine b ehavior at instruction level As part of the thesis work we have designed an in t e r m e d i a t e re p r e s e n t a t i o n I R for pro cessor sp ecication written in SimnML language The IR is simple and facilitates the development of various to ols such as assembler compiler backend generator instruction set simulator trace generator etc based on the pro
  • Differentiating Code from Data in X86 Binaries

    Differentiating Code from Data in X86 Binaries

    Differentiating Code from Data in x86 Binaries Richard Wartell, Yan Zhou, Kevin W. Hamlen, Murat Kantarcioglu, and Bhavani Thuraisingham Computer Science Department, University of Texas at Dallas, Richardson, TX 75080 {rhw072000,yan.zhou2,hamlen,muratk,bhavani.thuraisingham}@utdallas.edu Abstract. Robust, static disassembly is an important part of achieving high coverage for many binary code analyses, such as reverse engineering, malware analysis, reference monitor in-lining, and software fault isola- tion. However, one of the major difficulties current disassemblers face is differentiating code from data when they are interleaved. This paper presents a machine learning-based disassembly algorithm that segments an x86 binary into subsequences of bytes and then classifies each subse- quence as code or data. The algorithm builds a language model from a set of pre-tagged binaries using a statistical data compression technique. It sequentially scans a new binary executable and sets a breaking point at each potential code-to-code and code-to-data/data-to-code transition. The classification of each segment as code or data is based on the min- imum cross-entropy. Experimental results are presented to demonstrate the effectiveness of the algorithm. Keywords: statistical data compression, segmentation, classification, x86 binary disassembly. 1 Introduction Disassemblers transform machine code into human-readable assembly code. For some x86 executables, this can be a daunting task in practice. Unlike Java byte- code and RISC binary formats, which separate code and data into separate sections or use fixed-length instruction encodings, x86 permits interleaving of code and static data within a section and uses variable-length, unaligned in- struction encodings.