Risk
4/30/2013
11:45 PM
Connect Directly
RSS
E-Mail
50%
50%

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 lion's 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 firm's 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 Sonatype's 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 firm's 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, Sonatype's Jackson says. In the firm's 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 project's 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 you'd like to contact Dark Reading's editors directly, send us a message. Robert Lemos is a veteran technology journalist of more than 16 years and a former research engineer, writing articles that have appeared in Business Week, CIO Magazine, CNET News.com, Computing Japan, CSO Magazine, Dark Reading, eWEEK, InfoWorld, MIT's Technology Review, ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
Partner Perspectives
What's This?
In a digital world inundated with advanced security threats, Intel Security seeks to transform how we live and work to keep our information secure. Through hardware and software development, Intel Security delivers robust solutions that integrate security into every layer of every digital device. In combining the security expertise of McAfee with the innovation, performance, and trust of Intel, this vision becomes a reality.

As we rely on technology to enhance our everyday and business life, we must too consider the security of the intellectual property and confidential data that is housed on these devices. As we increase the number of devices we use, we increase the number of gateways and opportunity for security threats. Intel Security takes the “security connected” approach to ensure that every device is secure, and that all security solutions are seamlessly integrated.
Featured Writers
White Papers
Cartoon
Current Issue
Dark Reading's October Tech Digest
Fast data analysis can stymie attacks and strengthen enterprise security. Does your team have the data smarts?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-0334
Published: 2014-10-31
Bundler before 1.7, when multiple top-level source lines are used, allows remote attackers to install arbitrary gems by creating a gem with the same name as another gem in a different source.

CVE-2014-2334
Published: 2014-10-31
Multiple cross-site scripting (XSS) vulnerabilities in the Web User Interface in Fortinet FortiAnalyzer before 5.0.7 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, a different vulnerability than CVE-2014-2336.

CVE-2014-2335
Published: 2014-10-31
Multiple cross-site scripting (XSS) vulnerabilities in the Web User Interface in Fortinet FortiManager before 5.0.7 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, a different vulnerability than CVE-2014-2336.

CVE-2014-2336
Published: 2014-10-31
Multiple cross-site scripting (XSS) vulnerabilities in the Web User Interface in Fortinet FortiManager before 5.0.7 and FortiAnalyzer before 5.0.7 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, a different vulnerability than CVE-2014-2334 and CVE-2014-2335.

CVE-2014-3366
Published: 2014-10-31
SQL injection vulnerability in the administrative web interface in Cisco Unified Communications Manager allows remote authenticated users to execute arbitrary SQL commands via a crafted response, aka Bug ID CSCup88089.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Follow Dark Reading editors into the field as they talk with noted experts from the security world.