DOCSLIB.ORG

How to Write Secure Code in C

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
How to Write Secure Code in C WHITE PAPER How to Write Secure Code in C Introduction Software security is a top concern today. You can’t risk any security vulnerabilities — particularly if you’re developing software for embedded systems. And that means your code needs to be secure and free of coding errors. © Copyright Perforce Software, Inc. All trademarks and registered www.perforce.com trademarks are the property of their respective owners. WHITE PAPER How to Write Secure Code in C When you think about software security, you For example: probably think about passwords and access control. Or viruses, spoofing, and phishing attacks. char buff[10]; buff[10] = ‘a’; These are common security concerns. And secu- rity features, such data encryption and authenti- Here, an array of 10 bytes (index 0 to 9) is declared. cation protocols, mitigate these vulnerabilities. But the program then attempts to write a charac- ter one byte beyond the array’s boundary. If the But even if you’ve implemented these security memory neighboring the array is used later in the features, software can remain vulnerable. program, then it will lead to unexpected behavior. To ensure secure software, you need to start at This is bad enough. And it can get worse. A buffer the source — the code level. Otherwise, coding overflow can allow a hacker to take control of errors will compromise your program. a system. Coding Errors Compromise Security How Buffer Overflow Invites Hackers The Software Engineering Institute (SEI) Hackers can use buffer overflow errors to cause estimates that up to 90% of reported security a program to crash, corrupt the data, or simply incidents result from exploiting vulnerabilities in steal information. software code or design. And these vulnerabili- ties allow hackers to access private data or take When a program runs, it uses an area of memory unauthorized control of a system. referred to as the ‘stack’. Variables within the scope of the currently executing function will be So, a simple coding error can lead to a hacking stored on the stack. The address of the function threat. A hacker could take control of your call will also be stored to allow return statements computer, your home automation device, your to return to the correct location. home entertainment device, or your car. Worse still, a hacker could even take control of a nuclear When the function returns to the calling function, power plant. the program execution continues from where it left off. So, if the return address on the stack is EXAMPLE OF A SECURITY VULNERABILITY: modified to point to some alternative malicious BUFFER OVERFLOW IN C instructions, then those instructions will be To illustrate how this might happen, let’s look at executed when the function returns. just one example. Buffer overflow is a common security vulnerability in C programming. If the program is receiving data — and there is no check in place to ensure that the input buffer What Is Buffer Overflow? cannot overflow — then it will be possible to Buffer overflow occurs when data is written design an input, or ‘payload’, that contains mali- outside the boundary of the allocated memory. © Copyright Perforce Software, Inc. All trademarks and registered www.perforce.com trademarks are the property of their respective owners. WHITE PAPER How to Write Secure Code in C cious code. This overflows the input buffer and The top 25 list also adds a small set of the most overwrites the return address on the stack with effective ‘Monster Mitigations’. This helps devel- the address of the malicious code. opers reduce or eliminate entire groups of the top 25 weaknesses. It also helps with many of the PREVENTING SECURITY VULNERABILITIES other 800 weaknesses that are documented in the IS CRITICAL CWE list. Preventing security vulnerabilities — such as buf- fer overflow — is critical. And this can be done CWE focuses on stopping vulnerabilities at by making sure the code itself is written without the source. This is done by educating designers, exploitable gaps. programmers, and testers on how to eliminate common mistakes — before software is even After all, putting stronger locks on your front door is shipped. no use if the windows are left open. So, to improve security, you’ll need to ensure secure code. 2. CERT C You can apply the CERT C coding standard to 4 Ways to Ensure Secure Code in C your code. Writing secure code is important. And when it comes to C programming, there are four key sources of What Is CERT C? information to help you ensure secure code. The CERT C coding standard is published by the CERT Division at the Software Engineering 1. CWE Institute (SEI). SEI is a research and development You can identify security weaknesses from the center operated by Carnegie Mellon University. Common Weakness Enumeration (CWE). It’s primarily funded by the U.S. Department of Defense and the Department of Homeland What Is CWE? Security. CWE is a community-developed list of common software security weaknesses in C. It’s maintained CERT C Security Rules by the MITRE Corporation. This list can be used Secure coding experts continually develop the as a baseline for weakness identification, mitiga- CERT C guidelines on a wiki. tion, and prevention. Each guideline consists of: CWE’s List of Software Security Weaknesses • A title The CWE list prioritizes weaknesses. The top 25 • A description entries are prioritized using input from more than • An example of non-compliant code two dozen different organizations. They evaluate • Examples of compliant solutions each weakness based on frequency and impor- tance. Many of the weaknesses (in C programs) The guidelines cover coding and implementation listed in CWE relate to buffer overflow. errors, as well as low-level design errors. The aim © Copyright Perforce Software, Inc. All trademarks and registered www.perforce.com trademarks are the property of their respective owners. WHITE PAPER How to Write Secure Code in C is to eliminate in secure coding practices and C Secure Coding Rules undefined behaviors that can lead to vulnerabilities. ISO/IEC TS 179671:2013 includes rules for secure coding in C. It also includes examples for CERT C defines a each rule. vulnerability as: The purpose of C Secure is to specify secure A set of conditions that coding rules that can be automatically enforced. allows an attacker to violate These can be used to detect security flaws in C an explicit or implicit programming. To be considered a security flaw, a security policy. software bug must be triggerable by the actions of a malicious user or attacker. The defect may be minor. This means it doesn’t Analyzers that implement these rules must be affect the performance or results produced able to effectively discover secure coding errors by the software. But it nevertheless may be — without generating excessive false positives. exploited by an attack. And that results in a significant security breach. 4. MISRA C You can also use MISRA to ensure secure coding RECOMMENDED READING in C. Secure Coding in C and C++ What Is MISRA? by Robert Seacord MISRA provides best practice guidelines for the development of safety-related systems. Its C coding standards have been widely adopted across many industries. MISRA C Security Rules An essential resource for all C developers. MISRA C:2012 Amendment 1 was published in 2016. It provides additional security guidelines for C programming, including new rules and 3. ISO/IEC TS 17961:2013 “C SECURE” directives. It also includes examples of compliant You can apply the ISO/IEC TS 17961:2013 “C and non-compliant code. Secure” coding rules. These guidelines can be used to prevent coding What Is ISO/IEC TS 17961:2013? errors that lead to safety issues and security ISO/IEC TS 17961:2013 establishes a set of vulnerabilities. coding rules. These rules enable static code analyzers to diagnose insecure code beyond the requirements of the language standard. © Copyright Perforce Software, Inc. All trademarks and registered www.perforce.com trademarks are the property of their respective owners. WHITE PAPER How to Write Secure Code in C Why MISRA C Security Rules Are CWE-119: Improper Ideal for Embedded Systems Restriction of Operations MISRA C security rules are ideal for embedded within the Bounds of a systems. That’s because MISRA C security is on Memory Buffer par with that of other secure coding standards for C. Plus, MISRA C is trusted across embedded “The software performs op- systems industries. And it’s a go-to coding stan- erations on a memory buffer, dard in the automotive industry. but it can read from or write EXAMPLE OF A MISRA C SECURITY RULE to a memory location that MISRA C security rules can prevent coding errors is outside of the intended and security weaknesses, such as buffer overflow. boundary of the buffer.” Here’s an example of a MISRA C security rule: Following either the MISRA C rule or the CERT rule will ensure secure code — and avoid com- MISRA C Rule 18.1 mon weaknesses in CWE. This is because writing to an out-of-range pointer (or pointer operand) “A pointer resulting from could result in a buffer overflow — and vulner- arithmetic on a pointer oper- able code. Reading from an out-of-range pointer and shall address an element (or pointer operand) could accidentally reveal of the same array as that information to hackers. pointer operand.” So, by ensuring these rules are followed, you’ll avoid serious coding errors. You can enforce This rule does the same thing as the following MISRA and CERT rules by using a static code CERT C rule. analyzer, such as Helix QAC. ARR30-C COMPARING MISRA C AND OTHER STANDARDS “Do not form or use out-of- This is why the MISRA C coding standard is also ideal for environments where software security bounds pointers or array has more emphasis than safety.
Load more

Recommended publications
  • Vulnerability Assessment and Secure Coding Practices for Middleware Part 1
    Vulnerability Assessment and Secure Coding Practices for Middleware Part 1 James A. Kupsch Computer Sciences Department University of Wisconsin © 2007-2008, James A. K1upsch. All rights reserved. Tutorial Objectives • Show how to perform the basics of a vulnerability assessment • Create more people doing vulnerability assessments • Show how different types of vulnerabilities arise in a system • Teach coding techniques that can prevent certain types of vulnerabilities • Make your software more secure 2 Roadmap • Part 1: Vulnerability Assessment Process – Introduction – Evaluation process – Architectural analysis – Computer process – Communication channels – Resource analysis – Privilege analysis – Data Flow Diagrams – Component analysis – Vulnerability Discovery Activities • Part 2: Secure Coding Practices 3 Security Problems Are Real Everyone with a computer knows this. If you’re not seeing vulnerability reports and fixes for a piece of software, it doesn’t mean that it is secure. It probably means the opposite; they aren’t looking or aren’t telling. The grid community has been largely lucky (security through obscurity). 4 Many Avenues of Attack We’re looking for attacks that exploit inherent weakness in your system. Internet Firewall: www server Attack web using www protocols Compromised host Internal bad guy 5 Impact of Vulnerabilities FBI estimates computer security incidents cost U.S. businesses $67 billion in 2005 [CNETnews.com] Number of reported vulnerabilities each year is increasing [CERT stats] 8000 6000 4000 2000 0 1994 1998
    [Show full text]
  • Rogue Automation: Vulnerable and Malicious Code in Industrial
    In partnership with Rogue Automation Vulnerable and Malicious Code in Industrial Programming Federico Maggi Marcello Pogliani Trend Micro Research Politecnico di Milano Rogue Automation Vulnerable and Malicious Code in Industrial Programming Published by TREND MICRO LEGAL DISCLAIMER Trend Micro Research The information provided herein is for general information and educational purposes only. It is not intended and should not be construed to constitute legal advice. The information contained herein may not be applicable to all situations and may not reflect the most Written by current situation. Nothing contained herein should be relied on or acted upon without the benefit of legal advice based on the particular facts and circumstances presented and Federico Maggi nothing herein should be construed otherwise. Trend Micro reserves the right to modify Trend Micro Research the contents of this document at any time without prior notice. Marcello Pogliani Translations of any material into other languages are intended solely as a convenience. Politecnico di Milano Translation accuracy is not guaranteed nor implied. If any questions arise related to the accuracy of a translation, please refer to the original language official version of the document. Any discrepancies or differences created in the translation are not binding and With contributions from have no legal effect for compliance or enforcement purposes. Martino Vittone, Although Trend Micro uses reasonable efforts to include accurate and up-to-date Davide Quarta, information herein, Trend Micro makes no warranties or representations of any kind as to Stefano Zanero its accuracy, currency, or completeness. You agree that access to and use of and reliance Politecnico di Milano on this document and the content thereof is at your own risk.
    [Show full text]
  • Web Application Vulnerabilities and Insecure Software Root Causes: the OWASP Top 10
    Vulnerability Analysis, Secure Development and Risk Management of Web 2.0 Applications Marco Morana OWASP OWASP Cincinnati Chapter, November 2010 Meeting Copyright © 2010 - The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License. The OWASP Foundation http://www.owasp.org What is OWASP? OWASP 2 Agenda For Today’s Presentation 1. The Evolution of Web 2.0 2. Web 2.0 Vulnerability Analysis 3. Building Secure Web 2.0 Applications 4. Web 2.0 Risk Management OWASP 3 The Evolution of the Internet to Web 2.0 OWASP 4 General Web 2.0 Background Can be defined as: “Web applications that facilitate interactive information sharing and collaboration, interoperability, and user-centered design on the World Wide Web” … the main characteristics of web 2.0 are: 1. Encourage user’s participation and collaboration through a virtual community of social networks/sites. Users can and add and update their own content, examples include Twitter and social networks such as Facebook, Myspace, LinkedIn, YouTube 2. Transcend from the technology/frameworks used AJAX, Adobe AIR, Flash, Flex, Dojo, Google Gears and others 3. Combine and aggregate data and functionality from different applications and systems, example include “mashups” as aggregators of client functionality provided by different in-house developed and/or third party services (e.g. web services, SaaS) OWASP 5 Web 2.0 As Evolution of Human Knowledge Source http://digigogy.blogspot.com/2009/02/digital-blooms-visual.html
    [Show full text]
  • From Secure Coding to Secure Software
    From Secure Coding to Secure Software Table of Contents From Secure Coding to Secure Software ........................................................................................ 4 Why Software Security? .................................................................................................................. 6 Software and security failures are rampant ................................................................................... 7 Software and security failures are expensive ................................................................................. 8 Polling Question 2 ........................................................................................................................... 9 Engineering and Development ..................................................................................................... 10 Most Vulnerabilities Are Caused by Programming Errors ............................................................ 11 Secure Software Development ..................................................................................................... 12 Sources of Software Insecurity ..................................................................................................... 13 Polling Question 3 ......................................................................................................................... 15 Coding rules – 2016 Edition .......................................................................................................... 17 CWE Guidance ..............................................................................................................................
    [Show full text]
  • Vulnerabilities, Threats, and Secure Coding Practices
    Vulnerabilities, Threats, and Secure Coding Practices Barton P. Miller Elisa Heymann Computer Sciences Department Computer Sciences Department University of Wisconsin University of Wisconsin [email protected] & Universitat Autònoma de Barcelona [email protected] NSF CyberSecurity Summit 2015 Arlington, August 17 2015 1 What do we do • Assess Middleware: Make cloud/grid software more secure • Train: We teach tutorials for users, developers, sys admins, and managers • Research: Make in-depth assessments more automated and improve quality of automated code analysis http://www.cs.wisc.edu/mist/papers/VAshort.pdf 2 Our History 2001: “Playing Inside the Black Box” paper, first demonstration of hijacking processes in the Cloud. 2004: First formal funding from US NSF. 2004: First assessment activity, based on Condor, and started development of our methodology (FPVA). 2006: Start of joint effort between UW and UAB. 2006: Taught first tutorial at San Diego Supercomputer Center. 2007: First NATO funding, jointly to UAB, UW, and Ben Gurion University. 2008: First authoritative study of automated code analysis tools. 2009: Published detailed report on our FPVA methodology. 2009: U.S. Dept. of Homeland Security funding support. 2012: DHS Software Assurance Marketplace (SWAMP) research center. 3 Our experience includes Condor, University of Wisconsin Batch queuing workload management system 15 vulnerabilities 600 KLOC of C and C++ Google Chrome, Google Web browser 1 vulnerability 2396 KLOC of C and C++ MyProxy, NCSA Credential Management System 5 vulnerabilities
    [Show full text]
  • Software Analysis for Security
    Software Analysis for Security Spiros Mancoridis Department of Computer Science College of Engineering Drexel University Philadelphia, PA 19147, USA E-mail: [email protected] Abstract ware architecture to assure the system’s security. The qual- ity of a security architecture, however, also depends on the This is a survey of the processes, practices, and technolo- security of the applications that constitute the system. In gies that can help software maintenance engineers improve low security operating environments, such as most commer- the security of software systems. A particular emphasis is cial operating systems, it is assumed, albeit optimistically, placed on validating security architectures, verifying that that these applications are trustworthy. Therefore, it is im- the implementation of an architecture’s constituent appli- portant to articulate the practices to support the secure cod- cations adhere to secure coding practices, and protecting ing of applications and the tools for detecting malware. Se- software systems against malicious software. In addition to cure coding involves programming practices and run-time surveying the state-of-the-art, research challenges pertain- mechanisms that can be used to limit the vulnerabilityof ap- ing to software security are posed to the software mainte- plications to dangerous malware that exploit, for example, nance research community. buffer overflows, format string vulnerabilities, and integer vulnerabilities to attack computer systems. One approach to software security is to verify that (a) the security mechanisms used are trustworthy; (b) the security 1. Introduction architecture has been validated against the security policy; and (c) the software applications that constitute the system The goal of computer security is to protect computer as- are trustworthy (e.g., they have been developed using secure sets (e.g., servers, applications, web pages, data) from cor- coding practices, or they are not malware).
    [Show full text]
  • Security Training for Developers
    Security Training for Developers Trusted Advisor for All Your Information Security Needs ® ZERODAYLAB Increasing Cyber Resilience by Coding with the Hacker in Mind Our Security Training for Developers has a simple objective, educating software engineers to reinforce security best practice when developing software to reduce the accidental introduction of security vulnerabilities. By training your development team in the latest secure coding practices, you can bring your overall security costs down by: Reducing the number of incidents Conducting fewer penetration tests and re-tests as fewer vulnerabilities are found Changing the way developers think and increasing their ability to identify other risks Following best practice so that code has fewer bugs overall Using tried-and-tested methods to reduce the need for further corrective coding further down the line and resulting in a faster development cycle. Specialists in Face-to-Face Security Training ZeroDayLab delivers security training courses across the world for staff and management at all levels of an organisation, with or without technical knowledge. Drawn from a wealth of experience from the security projects we deliver for clients every day, we specialise in intensive, face-to-face training with specialist content designed to address the issues your organisation faces. ® ZERODAYLAB Security Training for Developers Security Training for Developers is a comprehensive, on-site training programme based around the 2017 OWASP Top 10. This two-day course will assess, educate and re-test to raise your software engineers’ information security knowledge. As a result, they will develop code with fewer vulnerabilities, expand their knowledge of current threats and tactics and learn hacking techniques.
    [Show full text]
  • Secure Coding Frameworks for the Development of Safe, Secure and Reliable Code
    Building Cybersecurity from the Ground Up Secure Coding Frameworks For the Development of Safe, Secure and Reliable Code Tim Kertis October 2015 The 27 th Annual IEEE Software Technology Conference Copyright © 2015 Raytheon Company. All rights reserved. Customer Success Is Our Mission is a registered trademark of Raytheon Company. Who Am I? Tim Kertis, Software Engineer/Software Architect Chief Software Architect, Raytheon IIS, Indianapolis Master of Science, Computer & Information Science, Purdue Software Architecture Professional through the Software Engineering Institute (SEI), Carnegie-Mellon University (CMU) 30 years of diverse Software Engineering Experience Advocate for Secure Coding Frameworks (SCFs) Author of the JAVA Secure Coding Framework (JSCF) Inventor of Cybersecurity thru Lexical And Symbolic Proxy (CLaSP) technology (patent pending) Secure Coding Frameworks 10/22/2015 2 Top 5 Cybersecurity Concerns … 1 - Application According to the 2015 ISC(2) Vulnerabilities Global Information Security 2 - Malware Workforce Study (Paresh 3 - Configuration Mistakes Rathod) 4 - Mobile Devices 5 - Hackers Secure Coding Frameworks 10/22/2015 3 Worldwide Market Indicators 2014 … Number of Software Total Cost of Cyber Crime: Developers: $500B (McCafee) 18,000,000+ (www.infoq.com) Cost of Cyber Incidents: Number of Java Software Low $1.6M Developers: Average $12.7M 9,000,000+ (www.infoq.com) High $61.0M (Ponemon Institute) Software with Vulnerabilities: 96% (www.cenzic.com) Secure Coding Frameworks 10/22/2015 4 Research
    [Show full text]
  • OWASP Secure Coding Practices Quick Reference Guide
    November 2010 OWASP Secure Coding Practices Quick Reference Guide Copyright and License Copyright © 2010 The OWASP Foundation. This document is released under the Creative Commons Attribution ShareAlike 3.0 license. For any reuse or distribution, you must make clear to others the license terms of this work. http://creativecommons.org/licenses/by-sa/3.0/ Version 2.0 1 November 2010 Table of Contents Introduction .................................................................................................. 3 Software Security and Risk Principles Overview ............................................. 4 Secure Coding Practices Checklist .................................................................. 5 Input Validation: .......................................................................................... 5 Output Encoding: ......................................................................................... 5 Authentication and Password Management: ..................................................... 6 Session Management:.................................................................................... 7 Access Control: ............................................................................................ 8 Cryptographic Practices: ................................................................................ 9 Error Handling and Logging: ......................................................................... 9 Data Protection:...........................................................................................10
    [Show full text]
  • Software Development Guidelines Jan 2019
    SECURE Software Development Guidelines Jan 2019 CONTENT 01 Introduction 02 Secure Software Development 03 Good coding practices 04 Principles of secure code design 05 Examples Secure Software Development Guidelines 2 01 Introduction Introduction Information technology is part of the life-blood The purpose of this presentation is to stand on of modern-day business operations. the shoulders of existing good practices, not Organisations are dependent on reliable and replace recognised ways of secure coding. This secure communications and IT systems. guide provides an overview of good working practices and techniques for assuring the Furthermore, the secure development of development of secure software. software is essential for ensuring the confidentiality, integrity, and availability of It is impractical to eliminate all security information processed within software vulnerabilities. However, by following applications, running upon information recognised good practices, this guide will communication technologies. facilitate changes in behaviours to reduce the likelihood of main security threats. Secure Software Development Guidelines 4 02 Secure Software Development and Standards Overview: Secure Development “Buffer overflows”, “zero-day vulnerabilities”, Secure software development is the art, rather “SQL injection”, are all buzz-words that signify than science, of reducing the likelihood of security problems in software that have systems compromise, given known, common, allowed, for example, a website, or a fat-client insecure development practices. application to become compromised and cracked into by an organised gang, an individual for financial or reputation gain. The sources of these attacks are many and varied (but are explored later on). However what they have in common is an open field to plough and reap financial gain from miss- configured, and insecurely programmed software applications.
    [Show full text]
  • Software Assurance: an Overview of Current Industry Best Practices
    Software Assurance: An Overview of Current Industry Best Practices February 2008 Executive Summary Software Assurance: An Overview of Current Industry Best Practices Software underpins the information infrastructure that govern- ments, critical infrastructure providers and businesses worldwide depend upon for daily operations and business processes. These organizations widely and increasingly use commercial off-the- shelf software (“COTS”) to automate processes with information technology. At the same time, cyber attacks are becoming more stealthy and sophisticated, creating a complex and dynamic risk environment for IT-based operations that users are working to better understand and manage. As such, users have become in- creasingly concerned about the integrity, security and reliability of commercial software. To address these concerns and meet customer requirements, vendors have undertaken significant efforts to reduce vulner- abilities, improve resistance to attack and protect the integrity of the products they sell. These efforts are often referred to as “software assurance.” Software assurance is especially impor- tant for organizations critical to public safety and economic and national security. These users require a high level of confidence that commercial software is as secure as possible, something only achieved when software is created using best practices for secure software development. This white paper provides an overview of how SAFECode mem- bers approach software assurance, and how the use of best practices for software
    [Show full text]
  • Oracle Software Security Assurance Oracle’S Methodology for the Development and Maintenance of Security in Its Products
    ORACLE BRIEF Oracle Software Security Assurance Oracle’s methodology for the development and maintenance of security in its products As organizations increasingly rely on software controls to protect their computing environments and data, ensuring that these controls operate in the way they were intended has become a paramount concern. Software security assurance encompasses all the activities involved in ensuring that software operates at an expected and predictable level of security. Managing security incidents, meeting complex regulatory and auditing requirements, and keeping current with security releases can add tremendous costs to an organization’s IT budget; thus organizations must give careful consideration to how their software providers approach software security assurance. Security built in, not bolted on S T A T I C CODE ANALYSIS Encompassing every phase of the product development lifecycle, Oracle Software Static security analysis of source code Security Assurance is Oracle's methodology for building security into the design, build, is used during the entire product testing, delivery, and maintenance of its products. Oracle's goal is to ensure that development cycle. This type of analysis works very well for identifying Oracle's products, as well as the customer systems that leverage those products, buffer overflows and memory leaks in remain as secure as possible. C/C++ code, resource handling issues Secure Coding Standards in J2EE and .NET, finding improper Secure software does not happen by itself. It requires consistently applied credentials handling, various injections, incorrect system configurations, etc. methodologies across each organization; methodologies that conform to stated policies, objectives, and principles. D Y N A M I C C O D E ANALYSIS Oracle Secure Coding Standards are a guide for developers in their efforts to produce Dynamic analysis activity always takes secure code.
    [Show full text]