DOCSLIB.ORG

Technology Infusion of Codesonar Into the Space Network Ground Segment (Technical Briefing)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Technology Infusion of Codesonar Into the Space Network Ground Segment (Technical Briefing) Technology Infusion of CodeSonar into the Space Network Ground Segment (Technical Briefing) Markland J. Benson / NASA GSFC 2009 Software Assurance Symposium Agenda Agenda Preliminaries (2) Environment (5) Goals (2) Approach (3) Applicability (2) Baseline (3) Findings (7) Conclusions (5) Wrap-Up (2) Environment-1 Agenda • Space network software must Preliminaries (2) support 24x7x365 operations with Environment (5) a high level of integrity, Goals (2) confidentiality, and availability Approach (3) • Current staff consists of 50 FTE to Applicability (2) sustain and enhance software Baseline (3) Programmer 30 Findings (7) • Approximately one-third of softwaTersete r 5 Conclusions (5) effort goes into discrepancy workC-M 5 Wrap-Up (2) SysAdmin 8 off and two-thirds to enhanced Management 2 capabilities Environment-2 Agenda • Scope: ground software systems that Preliminaries (2) control a satellite fleet and provide Environment (5) near earth communication services Goals (2) Approach (3) • Prioritized Responsibilities Applicability (2) Baseline (3) • Investigate operational issues Findings (7) • Resolve urgent operational issues Conclusions (5) Wrap-Up (2) • Provide enhanced capabilities for customers and operations • Resolve routine operational issues Environment-3 Volume IV Book 1 Local Operating Procedure 1 Agenda Capability Board Approved Change Preliminaries (2) Maturity Model Requirements Requirements Inspection Requirements Environment (5) Inspection Integrated, Six Checklist Goals (2) Design Preliminary Design Preliminary Inspection Inspection Design Approach (3) Sigma, and Checklist NASA standards Applicability (2) Detailed Design Detailed Inspection Design Baseline (3) and Static Analysis Tool Output Source Code Source Code Findings (7) requirements Inspection Conclusions (5) Source Code SCM Test are applied in Inspection Programmer Test Baseline Wrap-Up (2) software Checklist Software Test SCM Staging Software Test sustaining Plan Baseline Operational engineering Operational Test Test Plan Operational Baseline Environment-4 Agenda • Hours of loss due to software is 7% of Preliminaries (2) overall Environment (5) Goals (2) • The 7% slice of overall loss equates to Approach (3) 27% of the loss internal to the Space Applicability (2) Network [that which we directly control] Baseline (3) Findings (7) External Hardware Software Operations Conclusions (5) Wrap-Up (2) 74% 4% 7% 14% Environment-5 Agenda • Overall trend of software loss is down Preliminaries (2) Software Loss % Linear (Software Loss %) Environment (5) 60% Goals (2) 50% Approach (3) 40% Applicability (2) 30% Baseline (3) 20% Findings (7) 10% Conclusions (5) 0% 2003 2004 2005 2006 2007 2008 Wrap-Up (2) Percent internal loss due to software • Improvements in 2006 attributed to introduction of formal inspections Goals-1 Agenda • High availability and proficiency of Preliminaries (2) service requirements drive the need to Environment (5) reduce system defects Goals (2) Approach (3) Goal: Eliminate defects existing in the current Applicability (2) baseline software Baseline (3) • High demand for discrepancy Findings (7) resolution and new capabilities drive Conclusions (5) Wrap-Up (2) the need to produce software more quickly Goal: Eliminate defects earlier in the software development lifecycle (reduce rework) Goals-2 Agenda • Infuse automated source code Preliminaries (2) analysis technology Environment (5) Goals (2) • Provide for a uniform analysis toolset Approach (3) across languages and platforms Applicability (2) • Apply technology to systems that have Baseline (3) Findings (7) higher than average contribution to Conclusions (5) service loss Wrap-Up (2) • Minimize engineer time required to apply technology Approach-1 Agenda • GrammaTech’s CodeSonar product Preliminaries (2) provides mature analysis toolset for C Environment (5) and C++ (~50% of current code base) Goals (2) with new capability to cover Ada Approach (3) Applicability (2) (~30% of current code base) Baseline (3) Findings (7) Conclusions (5) Wrap-Up (2) • Software engineers use CodeSonar results as an input to the existing source code inspection process Approach-2 Agenda • Collect baseline information from the Preliminaries (2) sustaining engineering processes Environment (5) Goals (2) • Apply static analysis tool to a subset of Approach (3) the software baseline Applicability (2) • Review findings from the tool to Baseline (3) Findings (7) eliminate false positives and estimate Conclusions (5) future review time to be added to Wrap-Up (2) inspection process • Assess costs and benefits of larger deployment of analysis tools Approach-3 Agenda Apply study resources to Computer Preliminaries (2) Software Components (CSCs) known Environment (5) to be more troublesome than others Goals (2) Approach (3) Applicability (2) SW CSCI Hours Lost % Loss DR count % DRs KSLOC %KSLOC Baseline (3) CSCI A 6.126 37% 28 6% 200 2% Findings (7) CSCI B 0.910 5% 33 7% 64 1% Conclusions (5) Others 9.748 58% 398 87% 7865 97% Wrap-Up (2) Total 16.784 100% 459 100% 8129 100% Applicability-1 Agenda • The study is focused on large scale Preliminaries (2) software developed using formal Environment (5) processes Goals (2) Approach (3) • The systems studied are mission Applicability (2) critical in nature but some use Baseline (3) commodity computer systems Findings (7) Conclusions (5) • Linux, Windows, and VxWorks Wrap-Up (2) operating systems are represented • The application domain of the software is communications and spacecraft control systems Applicabilty-2 Agenda • If you have... Preliminaries (2) Environment (5) • in-house maintained software... Goals (2) • using a general purpose language... Approach (3) • with formal development process... Applicability (2) Baseline (3) • where failures lead to injury or Findings (7) significant financial loss... Conclusions (5) • ...this study has results that are Wrap-Up (2) directly meaningful to you. (even if #4 is not true for you, lower cost analyzers likely would be of benefit) Baseline -1 (What is SLOC anyway?) Agenda • SLOC definitions are inconsistent… Preliminaries (2) • David A. Wheeler’s SLOCCount tool Environment (5) Goals (2) and definition is used here: Approach (3) Physical SLOC is defined as follows: ``a physical source line of code (SLOC) is a line ending in a newline or end-of-file Applicability (2) marker, and which contains at least one non-whitespace non- Baseline (3) comment character.'' Comment delimiters (characters other than newlines starting and ending a comment) are considered Findings (7) comment characters. Data lines only including whitespace Conclusions (5) (e.g., lines with only tabs and spaces in multiline strings) are not included. Wrap-Up (2) • Non-Comment Source Lines (NCSL) == Physical SLOC • (Total) SLOC includes comments, blanks, and NCSL Baseline-2 Agenda • Productivity of software engineers is 0.16 Preliminaries (2) source lines of code (SLOC) per hour to Environment (5) perform requirements elicitation, design, Goals (2) coding, inspections, unit test, and Level 2 Approach (3) test Applicability (2) • Comparative industry productivity value is Baseline (3) 0.6 SLOC per hour by the German Findings (7) Aerospace Center Conclusions (5) Wrap-Up (2) • Difference can be attributed somewhat to evolving a product as opposed to new product development but productivity improvement is one of the goals Baseline-3 Agenda • In 2008, 204 software change Preliminaries (2) requests (CRs) were completed Environment (5) Goals (2) • Each CR produced an average of 209 Approach (3) new or modified lines of code Applicability (2) (changes to database values not Baseline (3) Findings (7) counted as SLOC modifications) Conclusions (5) • Formal inspections caused the Wrap-Up (2) removal of 1,255 defects from the code; 374 of the defects were classified as major (~30%) Findings-1 Agenda • For the 439 KSLOC (310 KNCSL) of Preliminaries (2) C/C++ code analyzed in 1,245 files, Environment (5) 1,011 findings were produced Goals (2) Approach (3) • All of 1,011 findings were reviewed Applicability (2) with an average review time of ~7 Baseline (3) minutes each All Findings Findings (7) 600 Conclusions (5) 500 Wrap-Up (2) 400 300 200 100 0 True Requires False Vendor Positive Research Positive Software Findings-2 Agenda • Requires Research findings were Preliminaries (2) classified as True or False Positive Environment (5) based on finding category Goals (2) Approach (3) • Vendor Software findings were Applicability (2) classified as False Positive Baseline (3) Findings (7) True Positive 600 Conclusions (5) 500 Wrap-Up (2) 400 300 200 100 0 Routine Urgent Findings-3 Agenda • Definition: An Urgent (a.k.a. major) Preliminaries (2) defect is one assessed as directly Environment (5) impacting availability or proficiency Goals (2) Approach (3) • Note: The large number of findings Applicability (2) and corresponding review time is not Baseline (3) expected to be repeated. Previously Findings (7) reviewed findings are filtered and only Conclusions (5) Wrap-Up (2) displayed if specifically requested Findings-4 Agenda Findings were not uniformly distributed Preliminaries (2) as a whole or proportionally among Environment (5) CSCs Goals (2) Approach (3) Component K-NCSL Defects / K-NCSL Applicability (2) CSCI B 121 1.8634 Baseline (3) Findings (7) CSCI A - CSC B 139 1.1571 Conclusions (5) CSCI A - CSC C 22 3.7156 Wrap-Up (2) CSCI A - CSC D 29 4.1332 NCSL = non-comment source lines Findings-5 200 Agenda 180 Preliminaries (2) 160 Environment (5) 140 Goals (2) 120 Approach (3) 100 80
Load more

Recommended publications
  • Undefined Behaviour in the C Language
    FAKULTA INFORMATIKY, MASARYKOVA UNIVERZITA Undefined Behaviour in the C Language BAKALÁŘSKÁ PRÁCE Tobiáš Kamenický Brno, květen 2015 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Vedoucí práce: RNDr. Adam Rambousek ii Acknowledgements I am very grateful to my supervisor Miroslav Franc for his guidance, invaluable help and feedback throughout the work on this thesis. iii Summary This bachelor’s thesis deals with the concept of undefined behavior and its aspects. It explains some specific undefined behaviors extracted from the C standard and provides each with a detailed description from the view of a programmer and a tester. It summarizes the possibilities to prevent and to test these undefined behaviors. To achieve that, some compilers and tools are introduced and further described. The thesis contains a set of example programs to ease the understanding of the discussed undefined behaviors. Keywords undefined behavior, C, testing, detection, secure coding, analysis tools, standard, programming language iv Table of Contents Declaration ................................................................................................................................ ii Acknowledgements .................................................................................................................. iii Summary .................................................................................................................................
    [Show full text]
  • Codesonar the SAST Platform for Devsecops
    DATASHEET CodeSonar The SAST Platform for DevSecOps Accelerate Application Security Software teams are under constant pressure to deliver more content with higher complexity, in shorter timeframes, with increased quality and security. Static Application Security Testing is a proven best practice to help software teams deliver the best code in the shortest timeframe. GrammaTech has been a leader in this field for over 15 years with CodeSonar delivering multi-language SAST capabilities for enterprises where software quality and software security matter. DevSecOps - Speed and Scale Language Support Software developers need rapid feedback on security CodeSonar supports many popular languages, including vulnerabilities in their code. CodeSonar can be integrated into C/C++, Java, C# and Android, as well as support for native software development environments, works unobtrusively to binaries in Intel, Arm and PowerPC instruction set architectures. the developer and provides rapid feedback. CodeSonar also supports OASIS SARIF, for exchange of information with other tools in the DevSecOps environment. Examples of Defects Detected • Buffer over- and underruns • Cast and conversion problems • Command injection • Copy-paste error • Concurrency • Ignored return value • Memory leak • Tainted data • Null pointer dereference • Dangerous function • Unused parameter / value And hundreds more Security Quality Privacy Broad coverage of security vulnerabilities, Integration into DevSecOps to improve Checkers that detect performance including OWASP Top10, SANS/CWE 25. quality of the code and developer impacts such as unnecessary test for Support for third party applications efficiency. Find code quality and nullness, creation of redundant objects or through byte code analysis. performance issues at speed. superfluous memory writes. Team Support Built In CodeSonar is designed to support large teams.
    [Show full text]
  • Grammatech Codesonar Product Datasheet
    GRAMMATECH CODESONAR PRODUCT DATASHEET Static Code Analysis and Static Application Security Testing Software Assurance Services Delivered by a senior software CodeSonar empowers teams to quickly analyze and validate the code – source and/or binary – engineer, the software assurance identifying serious defects or bugs that cause cyber vulnerabilities, system failures, poor services focus on automating reliability, or unsafe conditions. reporting on your software quality, creating an improvement plan and GrammaTech’s Software Assurance Services provide the benets of CodeSonar to your team in measuring your progress against that an accelerated timeline and ensures that you make the best use of SCA and SAST. plan. This provides your teams with reliable, fast, actionable data. GrammaTech will manage the static Enjoy the Benets of the Deepest Static Analysis analysis engine on your premises for you, such that your resources can Employ Sophisticated Algorithms Comply with Coding Standards focus on developing software. The following activities are covered: CodeSonar performs a unied dataow and CodeSonar supports compliance with standards symbolic execution analysis that examines the like MISRA C:2012, IS0-26262, DO-178B, Integration in your release process computation of the entire program. The US-CERT’s Build Security In, and MITRE’S CWE. Integration in check-in process approach does not rely on pattern matching or similar approximations. CodeSonar’s deeper Automatic assignment of defects analysis naturally nds defects with new or Reduction of parse errors unusual patterns. Review of warnings Analyze Millions of Lines of Code Optimization of conguration CodeSonar can perform a whole-program Improvement plan and tracking analysis on 10M+ lines of code.
    [Show full text]
  • Codesonar for C# Datasheet
    DATASHEET CodeSonar C# SAST when Safety and Security Matter Accelerate Application Security Software teams are under constant pressure to deliver more content with higher complexity, in shorter timeframes, with increased quality and security. Static Application Security Testing is a proven best practice to help software teams deliver the best code in the shortest timeframe. GrammaTech has been a leader in this field for over 15 years with CodeSonar delivering C# multi-language SAST capabilities for enterprises where software quality and software security matter. DevSecOps - Speed and Scale Abstract Interpretation Software developers need rapid feedback on security GrammaTech SAST tools use the concept of abstract vulnerabilities in their work artifacts. CodeSonar can be interpretation to statically examine all the paths through the integrated into software development environments, can work application and understand the values of variables and how they unobtrusively to the developer and provide rapid feedback. impact program state. Abstract interpretation gives CodeSonar for C# the highest scores in vulnerability benchmarks. Security Quality Privacy Broad coverage of security vulnerabilities, Integration into DevSecOps to improve Checkers that detect performance including OWASP Top10, SANS/CWE 25. quality of the code and developer impacts such as unnecessary test for Support for third party applications efficiency. Find code quality and nullness, creation of redundant objects or through byte code analysis. performance issues at speed. superfluous memory writes. Use Cases Enterprise customers are using C# in their internal applications, either in-house built, or built by a third-party. Static analysis is needed to to improve security and quality to drive business continuity. Mobile and Client customers are using C# on end-points, sometimes in an internet-of-things deployment, or to provide information to mobile users.
    [Show full text]
  • Software Vulnerabilities Principles, Exploitability, Detection and Mitigation
    Software vulnerabilities principles, exploitability, detection and mitigation Laurent Mounier and Marie-Laure Potet Verimag/Université Grenoble Alpes GDR Sécurité – Cyber in Saclay (Winter School in CyberSecurity) February 2021 Software vulnerabilities . are everywhere . and keep going . 2 / 35 Outline Software vulnerabilities (what & why ?) Programming languages (security) issues Exploiting a sofwtare vulnerability Software vulnerabilities mitigation Conclusion Example 1: password authentication Is this code “secure” ? boolean verify (char[] input, char[] passwd , byte len) { // No more than triesLeft attempts if (triesLeft < 0) return false ; // no authentication // Main comparison for (short i=0; i <= len; i++) if (input[i] != passwd[i]) { triesLeft-- ; return false ; // no authentication } // Comparison is successful triesLeft = maxTries ; return true ; // authentication is successful } functional property: verify(input; passwd; len) , input[0::len] = passwd[0::len] What do we want to protect ? Against what ? I confidentiality of passwd, information leakage ? I control-flow integrity of the code I no unexpected runtime behaviour, etc. 3 / 35 Example 2: make ‘python -c ’print "A"*5000’‘ run make with a long argument crash (in recent Ubuntu versions) Why do we need to bother about crashes (wrt. security) ? crash = consequence of an unexpected run-time error not trapped/foreseen by the programmer, nor by the compiler/interpreter ) some part of the execution: I may take place outside the program scope/semantics I but can be controled/exploited by an attacker (∼ “weird machine”) out of scope execution runtime error crash normal execution possibly exploitable ... security breach ! ,! may break all security properties ... from simple denial-of-service to arbitrary code execution Rk: may also happen silently (without any crash !) 4 / 35 Back to the context: computer system security what does security mean ? I a set of general security properties: CIA Confidentiality, Integrity, Availability (+ Non Repudiation + Anonymity + .
    [Show full text]
  • Code Review Guide
    CODE REVIEW GUIDE 2.0 RELEASE Project leaders: Larry Conklin and Gary Robinson Creative Commons (CC) Attribution Free Version at: https://www.owasp.org 1 F I 1 Forward - Eoin Keary Introduction How to use the Code Review Guide 7 8 10 2 Secure Code Review 11 Framework Specific Configuration: Jetty 16 2.1 Why does code have vulnerabilities? 12 Framework Specific Configuration: JBoss AS 17 2.2 What is secure code review? 13 Framework Specific Configuration: Oracle WebLogic 18 2.3 What is the difference between code review and secure code review? 13 Programmatic Configuration: JEE 18 2.4 Determining the scale of a secure source code review? 14 Microsoft IIS 20 2.5 We can’t hack ourselves secure 15 Framework Specific Configuration: Microsoft IIS 40 2.6 Coupling source code review and penetration testing 19 Programmatic Configuration: Microsoft IIS 43 2.7 Implicit advantages of code review to development practices 20 2.8 Technical aspects of secure code review 21 2.9 Code reviews and regulatory compliance 22 5 A1 3 Injection 51 Injection 52 Blind SQL Injection 53 Methodology 25 Parameterized SQL Queries 53 3.1 Factors to Consider when Developing a Code Review Process 25 Safe String Concatenation? 53 3.2 Integrating Code Reviews in the S-SDLC 26 Using Flexible Parameterized Statements 54 3.3 When to Code Review 27 PHP SQL Injection 55 3.4 Security Code Review for Agile and Waterfall Development 28 JAVA SQL Injection 56 3.5 A Risk Based Approach to Code Review 29 .NET Sql Injection 56 3.6 Code Review Preparation 31 Parameter collections 57 3.7 Code Review Discovery and Gathering the Information 32 3.8 Static Code Analysis 35 3.9 Application Threat Modeling 39 4.3.2.
    [Show full text]
  • Applications of SMT Solvers to Program Verification
    Nikolaj Bjørner Leonardo de Moura Applications of SMT solvers to Program Verification Rough notes for SSFT 2014 Prepared as part of a forthcoming revision of Daniel Kr¨oningand Ofer Strichman's book on Decision Procedures May 19, 2014 Springer Contents 1 Applications of SMT Solvers ............................... 5 1.1 Introduction . .5 1.2 From Programs to Logic . .6 1.2.1 An Imperative Programming Language Substrate. .6 1.2.2 Programs that are logic in disguise . .8 1.3 Test-case Generation using Dynamic Symbolic Execution . .9 1.3.1 The Application . .9 1.3.2 An Example . 10 1.3.3 Methodolgy. 11 1.3.4 Interfacing with SMT Solvers . 13 1.3.5 Industrial Adoption . 14 1.4 Symbolic Software Model checking . 15 1.4.1 The Application . 15 1.4.2 An Example . 15 1.4.3 Methodolgy. 16 1.4.4 Interfacing with SMT Solvers . 18 1.4.5 Industrial Adoption . 18 1.5 Static Analysis . 19 1.5.1 The Application . 19 1.5.2 An Example . 20 1.5.3 Methodolgy. 20 1.5.4 Interfacing with SMT Solvers . 22 1.5.5 Industrial Adoption . 22 1.6 Program Verification . 23 1.6.1 The Application . 23 1.6.2 An Example . 23 1.6.3 Methodolgy. 25 1.6.4 Bit-precise reasoning . 28 1.6.5 Industrial Adoption . 29 1.7 Bibliographical notes . 29 4 Contents References ..................................................... 31 1 Applications of SMT Solvers 1.1 Introduction A significant application domain for SMT solvers is in the analysis, verifi- cation, testing and construction of programs.
    [Show full text]
  • Report on the Third Static Analysis Tool Exposition (SATE 2010)
    Special Publication 500-283 Report on the Third Static Analysis Tool Exposition (SATE 2010) Editors: Vadim Okun Aurelien Delaitre Paul E. Black Software and Systems Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 October 2011 U.S. Department of Commerce John E. Bryson, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Under Secretary for Standards and Technology and Director Abstract: The NIST Software Assurance Metrics And Tool Evaluation (SAMATE) project conducted the third Static Analysis Tool Exposition (SATE) in 2010 to advance research in static analysis tools that find security defects in source code. The main goals of SATE were to enable empirical research based on large test sets, encourage improvements to tools, and promote broader and more rapid adoption of tools by objectively demonstrating their use on production software. Briefly, participating tool makers ran their tool on a set of programs. Researchers led by NIST performed a partial analysis of tool reports. The results and experiences were reported at the SATE 2010 Workshop in Gaithersburg, MD, in October, 2010. The tool reports and analysis were made publicly available in 2011. This special publication consists of the following three papers. “The Third Static Analysis Tool Exposition (SATE 2010),” by Vadim Okun, Aurelien Delaitre, and Paul E. Black, describes the SATE procedure and provides observations based on the data collected. The other two papers are written by participating tool makers. “Goanna Static Analysis at the NIST Static Analysis Tool Exposition,” by Mark Bradley, Ansgar Fehnker, Ralf Huuck, and Paul Steckler, introduces Goanna, which uses a combination of static analysis with model checking, and describes its SATE experience, tool results, and some of the lessons learned in the process.
    [Show full text]
  • Partner Directory Wind River Partner Program
    PARTNER DIRECTORY WIND RIVER PARTNER PROGRAM The Internet of Things (IoT), cloud computing, and Network Functions Virtualization are but some of the market forces at play today. These forces impact Wind River® customers in markets ranging from aerospace and defense to consumer, networking to automotive, and industrial to medical. The Wind River® edge-to-cloud portfolio of products is ideally suited to address the emerging needs of IoT, from the secure and managed intelligent devices at the edge to the gateway, into the critical network infrastructure, and up into the cloud. Wind River offers cross-architecture support. We are proud to partner with leading companies across various industries to help our mutual customers ease integration challenges; shorten development times; and provide greater functionality to their devices, systems, and networks for building IoT. With more than 200 members and still growing, Wind River has one of the embedded software industry’s largest ecosystems to complement its comprehensive portfolio. Please use this guide as a resource to identify companies that can help with your development across markets. For updates, browse our online Partner Directory. 2 | Partner Program Guide MARKET FOCUS For an alphabetical listing of all members of the *Clavister ..................................................37 Wind River Partner Program, please see the Cloudera ...................................................37 Partner Index on page 139. *Dell ..........................................................45 *EnterpriseWeb
    [Show full text]
  • Automatic Bug-Finding Techniques for Large Software Projects
    Masaryk University Faculty}w¡¢£¤¥¦§¨ of Informatics!"#$%&'()+,-./012345<yA| Automatic Bug-finding Techniques for Large Software Projects Ph.D. Thesis Jiri Slaby Brno, 2013 Revision 159 Supervisor: prof. RNDr. Antonín Kučera, PhD. Co-supervisor: assoc. prof. RNDr. Jan Strejček, PhD. ii Copyright c Jiri Slaby, 2013 All rights reservedtož to ja iii iv Abstract This thesis studies the application of contemporary automatic bug-finding techniques to large software projects. As they tend to be complex systems, there is a call for efficient analyzers that can exercise such projects without generating too many false positives. To fulfill these requirements, this thesis aims at the static analysis with the primary focus at techniques like the abstract interpretation and symbolic execution. Since their introduction in 1970’s, their applicability is increasing thanks to current fast processors and further improvements of the techniques. The thesis summarizes the current state of the art of chosen techniques implemented in the current static analyzers. Further, we discuss some large code bases which can be used as a test-bed for the techniques. Finally, we choose the Linux kernel. On the top of the explored state of the art, we de- velop our own techniques. We present the framework Stanse which utilizes the abstract interpretation and has no issues with handling the Linux kernel. The framework also prunes false positives resulting from some checkers. The pruning method is based on the pattern matching, but it turns out to be weak. Hence we subsequently try to improve the situation by the symbolic execution. For that purpose we use an executor called Klee in our new tool Symbiotic.
    [Show full text]
  • Softwaretest- & Analysetools Für Produktivität Und Qualität
    Softwaretest- & Analysetools für Produktivität und Qualität Statische Codeanalyse Dynamische Codeanalyse Software-Komplexitätsmessung Code Coverage www.verifysoft.com GrammaTech CodeSonar® GrammaTech CodeSonar® – Wenn Softwarequalität zum Prinzip erhoben wird Statische Analyse von Quell- und Binärcode Da die statische Analyse eine Ausführung der zu analysierenden (Teil-) Applikation nicht erfordert, kann CodeSonar bereits früh im Entwicklungsprozess kritische Softwarefehler aufdecken. Risiken, hervorgerufen durch z.B. gefährliche Sicherheitslücken, nichtdetermistische Nebenläufigkeitsfehler und Speicherlecks können so minimiert und hohe Wartungskosten, verursacht durch schwer lesbaren Code, vermieden werden. void gyroDisp(const char *sdf){ char* sBuffer; sBuffer = (char*) malloc(strlen(sdf)) + 1; if (!sBuffer){ exit(EXIT_FAILURE); } strcpy(sBuffer, sdf); /* Format string for LCD */ createLCD453Format(sBuffer); free(sBuffer); } f Kritische Fehler aufdecken f Nebenläufigkeitsprobleme erkennen f Sicherheitsschwachstellen eliminieren f Reports zur Zertifizierung nach ISO 26262 / DO-178C f Codierrichtlinien überprüfen generieren 4 | www.verifysoft.com GrammaTech CodeSonar® Statische Quellcodeanalyse HINTERGRUNDWISSEN Als führendes Werkzeug zur statischen Quellcodeanalyse Unterstützte Programmiersprachen f C/C++ f Java f C# weist CodeSonar im Vergleich zu vielen anderen stati- schen Analyse-Tools nicht nur eine bessere Fehlererken- Unterstützte Betriebssysteme nung auf, es zeichnet sich zudem durch eine vergleichs- f Windows f OS X weise geringe
    [Show full text]
  • Combining Binary Analysis Techniques to Trigger Use-After-Free Josselin Feist
    Finding the needle in the heap : combining binary analysis techniques to trigger use-after-free Josselin Feist To cite this version: Josselin Feist. Finding the needle in the heap : combining binary analysis techniques to trigger use- after-free. Cryptography and Security [cs.CR]. Université Grenoble Alpes, 2017. English. NNT : 2017GREAM016. tel-01681707v2 HAL Id: tel-01681707 https://tel.archives-ouvertes.fr/tel-01681707v2 Submitted on 12 Jan 2018 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. THESE` Pour obtenir le grade de DOCTEUR DE LA COMMUNAUTE´ UNIVERSITE´ GRENOBLE ALPES Specialit´ e´ : Informatique Arretˆ e´ ministerial´ : 25 mai 2016 Present´ ee´ par Josselin Feist These` dirigee´ par Marie-Laure Potet and Laurent Mounier prepar´ ee´ au sein Verimag et de Ecole´ Doctorale Mathematiques,´ Sciences et technologies de l’information, Informatique Finding the Needle in the Heap: Combining Binary Analysis Tech- niques to Trigger Use-After-Free These` soutenue publiquement le 29 mars 2017, devant le jury compose´ de : PHILIPPE ELBAZ-VINCENT Professeur,
    [Show full text]