Open Source Software Libraries Get Renewed Scrutiny

The Open Web Application Security Project adds common software components to its list of threats to spur developers to look more deeply at software libraries

As companies increasingly create applications and internal tools on top of open-source building blocks, vulnerabilities in those common components are becoming a serious threat.
Yet, the lions share of companies continue to ignore the problem, according to a report released this week. While nearly 80 percent of companies rely on open-source components for their development efforts, more than three-quarters lack any meaningful controls over the usage of such libraries and frameworks, according to the annual
Open Source Software Development Survey
conducted by Sonatype, a manager of a large repository of open-source components. While many companies have started to develop their own applications with security in mind, they have typically treated online components with less rigor, says Wayne Jackson, the firms CEO.
We have a very mature component-usage ecosystem, he says. Companies are getting enormous benefits from the ability to leverage byte-sized innovation ... but the ecosystem to support that consumption, to bring order to all of that, is completely missing.
The Open Web Application Security Project has recognized the threat as well. For the first time since the group began compiling its OWASP Top-10 List of Web security weaknesses, the list has singled out
software components with known vulnerabilities
as a top threat in its 2013 list of candidates. For example, two vulnerabilities--Apache CXF Authentication Bypass and the Spring Remote Code Execution--affected components that were downloaded 22 million times in 2011, the group noted.
Virtually every application has these issues because most development teams don’t focus on ensuring their components stay up to date, the OWASP entry reads. In many cases, the developers don’t even know all the components they are using, never mind their versions.
[Poor communication and significant friction between developers and the software-security team is a key reason that software issues continue to go unaddressed. See
Building A Detente Between Developers And Security
.]
The problem will only be made worse by the growing popularity of common components and libraries. In 2012, use of components skyrocketed. From Sonatypes repository alone, some 8 billion software components were downloaded during the year, almost doubling the number of components downloaded in 2011, the firm states.
Solving the problem will be hard. Companies should not rely on the open-source project to get it right. While open-source developers like to trust in many eyes that peruse the code to catch most vulnerabilities, only a few projects garner enough attention for contributors to catch a good percentage of security flaws, says Chris Wysopal, chief technology officer and co-founder of application-security firm Veracode.
The many eyes theory only works for the very largest projects, Wysopal says.
Companies should instead treat open-source components and libraries in a similar way to the firms own code and analyze them for vulnerabilities, Wysopal adds. If you are doing static or dynamic analysis on the code you are writing, you need to do the same thing to the open-source software that is coming into your environment, he says.
Security teams need to work with the developers to make sure that open-source policies are both enforceable and do not slow down development so much that programmers attempt to go around the policies, Sonatypes Jackson says. In the firms study, developers listed enforcing policies, slower development and the delayed notification of vulnerabilities as the top-3 issues affecting implementation of open-source policies.
In the end, companies must be prepared to check the components themselves, rather than trust an open-source projects maintainers to find all the bugs, agrees Jacob West, chief technology officer of the Enterprise Security Products group at Hewlett-Packard.
For the foreseeable future, the onus is on the organization to determine how much risk open-source components produce, West says.
Have a comment on this story? Please click Add Your Comment below. If youd like to contact
Dark Readings
editors directly,
send us a message
.

Last News
▸ Microsoft to fix 40 flaws on Tuesday ◂ Discovered: 05/01/2025 Category: security	▸ Sandia Labs Makes Tiny Battery. ◂ Discovered: 05/01/2025 Category: security	▸ Dual security: 2FA is necessary but not sufficient ◂ Discovered: 05/01/2025 Category: security

**Cyber Security Categories**
Google Dorks Database	Exploits Vulnerability	Exploit Shellcodes

CVE List

Tools/Apps

News/Aarticles

Phishing Database

Deepfake Detection

Trends/Statistics & Live Infos

Tags:
Open Source Software Libraries Get Renewed Scrutiny