The sorry state of affairs of software components

Synopsys has released its report, “The State of Software Composition 2017,” which analyses real-world data to investigate the security of the software supply chain ­ one of the most significant challenges the software industry faces today. The report summarises the analysis of 128,782 software applications, which identified 16,868 unique versions of open source and commercial software components containing almost 10,000 unique security vulnerabilities.

  • 7 years ago Posted in
Synopsys used its software composition analysis product, Protecode SC, to analyse applications scanned from January 1, 2016 through December 31, 2016. Of the 3rd party software components identified through the analysis of these applications, nearly 50 percent of these components were more than four years old, and in almost every case a newer, more secure version of the software component is available.
“By analysing large data sets and identifying trends and problem areas, we are able to provide the software development community with valuable intelligence to help them keep their software secure and up to date,” said Andreas Kuehlmann, senior vice president and general manager for the Synopsys Software Integrity Group. “Over time, vulnerabilities in third-party components are discovered and disclosed, leaving a previously secure software package open to exploits. The message to the software industry should not be whether to use open source software, but whether you are vigilant about keeping it updated to prevent attacks.”  
The research, upon which the report is based, represents a cross section of software including mobile, desktop and web applications, as well as firmware and embedded software from a variety of industries. The report includes information on the most commonly observed 3rd party software components, the Common Vulnerabilities and Exposures (CVE) known to affect these components, the 10-point Common Vulnerability Scoring System (CVSS) rank for CVE and the Common Software Weaknesses (CWE) used to classify them.
Other key findings include:
  • 45 percent of the total 9,553-specific CVEs date back to 2013 or earlier
  • The Heartbleed bug still appears in the top 50 percent of all CVEs observed, even though a patch has been available since 2014
  • The oldest CVE dates back to 1999
  • The top 10 most common software components with outdated versions still being used more than 90 percent of the time include: Curl, Dropbear, Expat, libjpeg-turbo, libjpeg, libpng Linux Kernal, Lua, OpenSSL, and Pcre; if they are not updated, these software components may leave products vulnerable
“Coming on the heels of last month’s WannaCry outbreak, the insights in the report serve as a wakeup call that not everyone is using the most secure version of available software,” said Robert Vamosi, security strategist at Synopsys. “The update process does not end at the time of software release, and an ongoing pattern of software updates must be implemented throughout the product lifecycle. As new CVEs are disclosed against open source software components, developers need to know whether their products are affected, and organisations need to prevent the exploit of vulnerabilities with the latest versions when they become available.”
Talent and training partner, mthree, which supports major global tech, banking, and business...
On average, only 48% of digital initiatives meet or exceed business outcome targets, according to...
Humans may do a lot less of the testing themselves in the future, but they will still have to peer...
JFrog has released the findings of an IDC survey indicating developers are spending significantly...
New research from Mendix finds that low-code tools are no longer simply a tactical solution for...
Global study of over 1,300 tech professionals uncovers opportunities for enhanced security training...
Global IT Business-to-Business (B2B) revenues, coming from data centers, IT services and devices,...
Confluent adds Table API support for Apache Flink® making it even easier for developers to use...