Endpoint //

Privacy

3/9/2015
04:50 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

OpenSSL To Undergo Major Audit

The Linux Foundation's Core Infrastructure Initiative funding work to take a closer look at the TLS stack.

The first major public audit of OpenSSL will soon be underway, backed by the Linux Foundation's Core Infrastructure Initiative -- a $1.2 million open-source research fund established last spring in the wake of Heartbleed. The audit will be one of the first well-funded efforts to harden open-source infrastructure, historically financed only by researchers' free time, sense of civic duty, and community spirit. 

"The amount of time and work this is going to take, just trying to do it on nights and weekends is not going to yield good results," says Tom Ritter, principal security consultant of NCC Group, which is part of Cryptography Services, the team conducting the audit.

In April 2014, 12 leading technology firms -- Amazon Web Services, Cisco, Dell, Facebook, Fujitsu, Google, IBM, Intel, Microsoft, NetApp, RackSpace, and VMware -- agreed to contribute $100,000 apiece per year, for the next three years, to the Initiative. 

When deciding where those resources would go, "OpenSSL was the frontrunner," says Ritter. "It hadn't had as much attention paid to it as it should have."

Never was that clearer than last year when the critical Heartbleed vulnerability in OpenSSL's implementation of the Transport Layer Security (TLS) protocol's "heartbeat" extension was discovered. Although Ritter says the team does not know what they'll find when they begin the audit, clearly Heartbleed is part of their thought process; as Ritter explained in a blog post today:

The audit’s primary focus is on the TLS stacks, covering protocol flow, state transitions, and memory management. We’ll also be looking at the BIOs, most of the high-profile cryptographical algorithms, and setting up fuzzers for the ASN.1 and x509 parsers.

"If you do an audit," says Ritter, "you get the most value out of it if you've done some preparation." The OpenSSL community has done such preparation, he says, by hiring more staff and completing a reformatting of its codebase earlier this month.

Ritter says the audit will take several months to complete, and expects to publish results over the summer.  

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Charlie Babcock
50%
50%
Charlie Babcock,
User Rank: Ninja
3/10/2015 | 12:28:13 PM
How about supporting OpenSSL
A bit of a rebuke to open source practices: "just doing it at night and on weekends" isn't going to cut it. A new worry is taking hold that some open source isn't maintained professionally enough. The answer might be to provide more support to the open source programmers knowledgeable in the code. OpenSSL, for all its widespread use, was getting about $2,000 a year in support in donations. That's an indictment of all those who use it without understanding its slender base of support.
robrjay
50%
50%
robrjay,
User Rank: Apprentice
3/16/2015 | 9:47:19 AM
Re: How about supporting OpenSSL
I agree it's an inictment of those that have used it withouth contributing. However, I thing it's a good thing it's getting an proper audit. The contributing organizations all have skin in the game now. It will benefit their businesses as well as general public in helping to make it more secure. We all win.  
Is Threat Intelligence Garbage?
Chris McDaniels, Chief Information Security Officer of Mosaic451,  5/23/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
What Israel's Elite Defense Force Unit 8200 Can Teach Security about Diversity
Lital Asher-Dotan, Senior Director, Security Research and Content, Cybereason,  5/21/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Shhh!  They're watching... And you have a laptop?  
Current Issue
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-3018
PUBLISHED: 2018-05-24
The AXIS webapp in deploy-tomcat/axis in IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.1.2 and 7.2.0 through 7.2.1.4 allows remote attackers to obtain sensitive configuration information via a direct request, as demonstrated by happyaxis.jsp. IBM X-Force ID: 84354.
CVE-2013-3023
PUBLISHED: 2018-05-24
IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.1.2 and 7.2.0 through 7.2.1.4 might allow remote attackers to obtain sensitive information about Tomcat credentials by sniffing the network for a session in which HTTP is used. IBM X-Force ID: 84361.
CVE-2013-3024
PUBLISHED: 2018-05-24
IBM WebSphere Application Server (WAS) 8.5 through 8.5.0.2 on UNIX allows local users to gain privileges by leveraging improper process initialization. IBM X-Force ID: 84362.
CVE-2018-5674
PUBLISHED: 2018-05-24
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Foxit Reader before 9.1 and PhantomPDF before 9.1. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw...
CVE-2018-5675
PUBLISHED: 2018-05-24
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Foxit Reader before 9.1 and PhantomPDF before 9.1. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw...