VB2014 preview: The three levels of exploit testing

Posted by   Virus Bulletin on   Sep 9, 2014

Richard Ford and Marco Carvalho present an idea for how to test products that claim to detect the unknown.

In the weeks running up to VB2014 (the 24th Virus Bulletin International Conference), we are looking at some of the research that will be presented at the event. Today, we look at the paper 'The three levels of exploit testing', by Richard Ford and Marco Carvalho from the Florida Institute of Technology.

Whether you're worried about China's 'Comment Crew', or state-sanctioned hackers from Fort Meade, MD, the use of zero-day exploits against your organisation is a worst-case scenario. Thankfully, a number of companies have developed solutions that claim to detect the unknown: they will detect attacks using unknown exploits of unknown vulnerabilities.

But are such products any good?

This question isn't easy to answer. From an attacker's point of view, the ideal zero-day exploit leaves no trace - so, in tests, the fact that a product has missed it won't be detected.

Getting hold of zero-days to use in a lab environment, also comes with various ethical issues: the morally right thing to do is to report the vulnerabilities to the affected vendor. Moreover, it is an understatement to say that finding such vulnerabilities for testing purposes scales rather badly.

Richard Ford, VB2013
  Are you sure you want try your zero-days against Richard Ford?

In their paper, Richard and Marco describe a new approach: they suggest using popular open-source software, then modifying the source code and, while doing so, deliberately inserting a new vulnerability, known to the tester, but unknown to the product that is to be tested.

By using the CVE list, the testers should be able to make sure the vulnerabilities they insert are similar in type to those that are commonly seen. They could also design a test that measures detection of a specific class of vulnerabilities.

As everyone in security knows, almost all attacks seen in the wild exploit known (and usually patched) vulnerabilities. However, it is detection of zero-day vulnerabilities that people are most concerned about (and about which vendors tend to make very bold claims). Richard and Marco's paper presents a neat idea to test such claims.

Registration for VB2014 is still open.

Posted on 09 September 2014 by Martijn Grooten

twitter.png
fb.png
linkedin.png
googleplus.png
reddit.png

 

Latest posts:

Red Eyes threat group targets North Korean defectors

A research paper by AhnLab researcher Minseok Cha looks at the activities of the Red Eyes threat group (also known as Group 123 and APT 37), whose targets include North Korean defectors, as well as journalists and human rights defenders focused on…

VB announces Threat Intelligence Summit to take place during VB2018

We are very excited to announce a special summit, as part of VB2018, that will be dedicated to all aspects of threat intelligence.

VB2018 Small Talk: An industry approach for unwanted software criteria and clean requirements

An industry approach for defining and detecting unwanted software to be presented and discussed at the Virus Bulletin conference.

VB2018 call for last-minute papers opened

The call for last-minute papers for VB2018 is now open. Submit before 2 September to have your abstract considered for one of the nine slots reserved for 'hot' research.

VB2017 paper and update: Browser attack points still abused by banking trojans

At VB2017, ESET researchers Peter Kálnai and Michal Poslušný looked at how banking malware interacts with browsers. Today we publish their paper, share the video of their presentation, and also publish a guest blog post from Peter, in which he…

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.