This document discusses Coverity's participation in the 2010 Software Assurance Technology Experiment (SATE). It summarizes that Coverity analyzed significantly more code in 2010 than 2009, including Chrome, Wireshark, and Dovecot. Coverity's tools are freely available to SATE researchers. The results found around 2300 total defects, with 1900 being high or medium impact. Only around 1% of defects were selected for SATE. It recommends establishing a defect catalog by thoroughly triaging one codebase per language. It also suggests improving Common Vulnerabilities and Exposures (CVE) triage and providing virtual machines to analyze code.
1 of 12
Download to read offline
More Related Content
Coverity's Software Integrity Ratings
1. 息 Coverity 2010
Coverity Analysis: Improving Quality in
the Software Supply Chain
Peter Henriksen, Development Manager for Analysis, Coverity
October 1, 2010
3. 3
Importance of SATE
3ALL MATERIALS CONFIDENTIAL
Helping the Space Mature
Important to have broad participation
Transparency
Pushing the envelope
Coverity Participation
Significant amount of work (~20 times more than 2009!)
C/C++ Track: Chrome, Wireshark & Dovecot
Coverity tools freely available for SATE researchers
4. 4
SATE 2010: Listening to the Community
4ALL MATERIALS CONFIDENTIAL
Improved Classification
Security/Quality/Insignificant/False Positive
Broader Language Coverage
C, C++ & Java
Larger Code Bases
Addition of Chrome: large code base, widely used
CVE
Healthy challenge!
5. 5
Coverity SATE Results: C/C++ Track
5ALL MATERIALS CONFIDENTIAL
SATE 2010 Selection: 30-40bugs
Improved SATE triage with new Quality classification
General agreement on the triage results
Number of Bugs
Total (estimated TP): ~2300
High & Medium Impact: ~1900
SATE selection: ~1%
Triage is hard!
Quality of event messages is important
Impact assessment is essential
7. 7
The Software Supply Chain
7ALL MATERIALS CONFIDENTIAL
The Problem
Weakest link in the chain
Defects in shared libraries can impact millions of devices
(computers, phones, etc)
How Coverity Can Help
Integrity Report with Integrity Rating
Software Certification
Upstream Elimination of Defects
Open source
3rd party
Company wide libraries
10. 10
How to Use Your Software Integrity Rating
10ALL MATERIALS CONFIDENTIAL
Set software integrity standards for your projects,
products and teams
Audit your software supply chain
Promote your commitment to software integrity
11. 11
Next Steps for SATE
11ALL MATERIALS CONFIDENTIAL
Defect (& FP) Catalog
Select one code base (per language)
Fix the version
Perform deep & thorough triage
Resulting contents: Tools + Manual + CVE + FP
Minor Recommendations
Improve the CVE triage
More time (add 4-6 weeks)
Make Ubuntu VmWare VMs available for C/C++ Track