Category Archives: vFeed

Overview

In case you haven’t guessed by now, I am an unadulterated tools nerd. Hopefully, ten years of toolsmith have helped you come to that conclusion on your own. I rejoice when I find like-minded souls, I found one in Nabil (NJ) Ouchn (@toolswatch), he of Black Hat Arsenal and toolswatch.org fame. In addition to those valued and well-executed community services, NJ also spends a good deal of time developing and maintaining vFeed. vFeed included a Python API and the vFeed SQLite database, now with support for Mongo. It is, for all intents and purposes a correlated community vulnerability and threat database. I’ve been using vFeed for quite a while now having learned about it when writing about FruityWifi a couple of years ago.
NJ fed me some great updates on this constantly maturing product.
Having achieved compatibility certifications (CVE, CWE and OVAL) from MITRE, the vFeed Framework (API and Database) has started to gain more than a little gratitude from the information security community and users, CERTs and penetration testers. NJ draws strength from this to add more features now and in the future. The actual vFeed roadmap is huge. It varies from adding new sources such as security advisories from industrial control system (ICS) vendors, to supporting other standards such as STIX, to importing/enriching scan results from 3rd party vulnerability and threat scanners such as Nessus, Qualys, and OpenVAS.
There have a number of articles highlighting impressive vFeed uses cases of vFeed such as:

• Affordable Security: Making the most of free tools and data (Splunk & Nessus)
• Applying Data Analytics on Vulnerability Data (Enhancing data analytics for vulnerability management, from SANS)
• SimaticScan (using vFeed data to create an industrial PLC security scanner)
• Correlation and Visualization using vFeed 

Needless to say, some fellow security hackers and developers have included vFeed in their toolkit, including Faraday (March 2015 toolsmith), Kali Linux, and more (FruityWifi as mentioned above).

The upcoming version vFeed will introduce support for CPE 2.3, CVSS 3, and new reference sources. A proof of concept to access the vFeed database via a RESTFul API is in testing as well. NJ is fine-tuning his Flask skills before releasing it. 🙂 NJ, does not consider himself a Python programmer and considers himself unskilled (humble but unwarranted). Luckily Python is the ideal programming language for someone like him to express his creativity.
I’ll show you all about woeful programming here in a bit when we discuss the vFeed Viewer I’ve written in R.

First, a bit more about vFeed, from its Github page:
The vFeed Framework is CVE, CWE and OVAL compatible and provides structured, detailed third-party references and technical details for CVE entries via an extensible XML/JSON schema. It also improves the reliability of CVEs by providing a flexible and comprehensive vocabulary for describing the relationship with other standards and security references.
vFeed utilizes XML-based and  JSON-based formatted output to describe vulnerabilities in detail. This output can be leveraged as input by security researchers, practitioners and tools as part of their vulnerability analysis practice in a standard syntax easily interpreted by both human and machine.
The associated vFeed.db (The Correlated Vulnerability and Threat Database) is a detective and preventive security information repository useful for gathering vulnerability and mitigation data from scattered internet sources into an unified database.
vFeed’s documentation is now well populated in its Github wiki, and should be read in its entirety:

1. vFeed Framework (API & Correlated Vulnerability Database)
2. Usage (API and Command Line)
3. Methods list
4. vFeed Database Update Calendar

vFeed features include:

• Easy integration within security labs and other pentesting frameworks 
• Easily invoked via API calls from your software, scripts or from command-line. A proof of concept python api_calls.py is provided for this purpose
• Simplify the extraction of related CVE attributes
• Enable researchers to conduct vulnerability surveys (tracking vulnerability trends regarding a specific CPE)
• Help penetration testers analyze CVEs and gather extra metadata to help shape attack vectors to exploit vulnerabilities
• Assist security auditors in reporting accurate information about findings during assignments. vFeed is useful in describing a vulnerability with attributes based on standards and third-party references(vendors or companies involved in the standardization effort)

For reference material…

from lib.core.methods.ref import CveRef

cve = “CVE-2008-0793”

ref = CveRef(cve).get_refs()

print ref

I thought I’d get started on a user interface for vFeed using R and Shiny, appropriately name vFeed Viewer and found on Github here. This first version does not allow direct queries of the vFeed database as I’m working on SQL injection prevention, but it does allow very granular filtering of key vFeed tables. Once I work out safe queries and sanitization, I’ll build the same full correlation features you enjoy from NJ’s Python vFeed client.
You’ll need a bit of familiarity with R to make use of this viewer.
First install R, and RStudio.  From the RStudio console, to ensure all dependencies are met, run install.packages(c(“shinydashboard”,”RSQLite”,”ggplot2″,”reshape2″)).
Download and install the vFeed Viewer in the root vFeed directory such that app.R and the www directory are side by side with vfeedcli.py, etc. This ensures that it can read vfeed.db as the viewer calls it directly with dbConnect and dbReadTable, part of the RSQLite package.
Open app.R with RStudio then, click the Run App button. Alternatively, from the command-line, assuming R is in your path, you can run R -e “shiny::runApp(‘~/shinyapp’)” where ~/shinyapp is the path to where app.R resides. In my case, on Windows, I ran R -e “shiny::runApp(‘c:\\tools\\vfeed\\app.R’)”. Then browser to the localhost address Shiny is listening on. You’ll probably find the RStudio process easier and faster.
One important note about R, it’s not known for performance, and this app takes about thirty seconds to load. If you use Microsoft (Revolution) R with the MKL library, you can take advantage of multiple cores, but be patient, it all runs in memory. Its fast as heck once it’s loaded though.
The UI is simple, including an overview.

At present, I’ve incorporated NVD and CWE search mechanisms that allow very granular filtering.

 As an example, using our favorite CVE-2008-0793, we can zoom in via the search field or the CVE ID drop down menu. Results are returned instantly from 76,123 total NVD entries at present.

From the CWE search you can opt to filter by keywords, such as XSS for this scenario, to find related entries. If you drop cross-site scripting in the search field, you can then filter further via the cwetitle filter field at the bottom of the UI. This is universal to this use of Shiny, and allows really granular results.

You can also get an idea of the number of vFeed entries per vulnerability category entities. I did drop CPEs as their number throws the chart off terribly and results in a bad visualization.

I’ll keep working on the vFeed Viewer so it becomes more useful and helps serve the vFeed community. It’s definitely a work in progress but I feel as if there’s some potential here.

Conslusion

Thanks to NJ for vFeed and all his work with the infosec tools community, if you’re going to Black Hat be certain to stop by Arsenal. Make use of vFeed as part of your vulnerability management practice and remember to check for updates regularly. It’s a great tool, and getting better all the time.
Ping me via email or Twitter if you have questions (russ at holisticinfosec dot org or @holisticinfosec).
Cheers…until next month.

Acknowledgements

Nabil (NJ) Ouchn (@toolswatch)

Continue reading toolsmith #116: vFeed & vFeed Viewer→

Overview

In case you haven’t guessed by now, I am an unadulterated tools nerd. Hopefully, ten years of toolsmith have helped you come to that conclusion on your own. I rejoice when I find like-minded souls, I found one in Nabil (NJ) Ouchn (@toolswatch), he of Black Hat Arsenal and toolswatch.org fame. In addition to those valued and well-executed community services, NJ also spends a good deal of time developing and maintaining vFeed. vFeed included a Python API and the vFeed SQLite database, now with support for Mongo. It is, for all intents and purposes a correlated community vulnerability and threat database. I’ve been using vFeed for quite a while now having learned about it when writing about FruityWifi a couple of years ago.
NJ fed me some great updates on this constantly maturing product.
Having achieved compatibility certifications (CVE, CWE and OVAL) from MITRE, the vFeed Framework (API and Database) has started to gain more than a little gratitude from the information security community and users, CERTs and penetration testers. NJ draws strength from this to add more features now and in the future. The actual vFeed roadmap is huge. It varies from adding new sources such as security advisories from industrial control system (ICS) vendors, to supporting other standards such as STIX, to importing/enriching scan results from 3rd party vulnerability and threat scanners such as Nessus, Qualys, and OpenVAS.
There have a number of articles highlighting impressive vFeed uses cases of vFeed such as:

• Affordable Security: Making the most of free tools and data (Splunk & Nessus)
• Applying Data Analytics on Vulnerability Data (Enhancing data analytics for vulnerability management, from SANS)
• SimaticScan (using vFeed data to create an industrial PLC security scanner)
• Correlation and Visualization using vFeed 

Needless to say, some fellow security hackers and developers have included vFeed in their toolkit, including Faraday (March 2015 toolsmith), Kali Linux, and more (FruityWifi as mentioned above).

The upcoming version vFeed will introduce support for CPE 2.3, CVSS 3, and new reference sources. A proof of concept to access the vFeed database via a RESTFul API is in testing as well. NJ is fine-tuning his Flask skills before releasing it. 🙂 NJ, does not consider himself a Python programmer and considers himself unskilled (humble but unwarranted). Luckily Python is the ideal programming language for someone like him to express his creativity.
I’ll show you all about woeful programming here in a bit when we discuss the vFeed Viewer I’ve written in R.

First, a bit more about vFeed, from its Github page:
The vFeed Framework is CVE, CWE and OVAL compatible and provides structured, detailed third-party references and technical details for CVE entries via an extensible XML/JSON schema. It also improves the reliability of CVEs by providing a flexible and comprehensive vocabulary for describing the relationship with other standards and security references.
vFeed utilizes XML-based and  JSON-based formatted output to describe vulnerabilities in detail. This output can be leveraged as input by security researchers, practitioners and tools as part of their vulnerability analysis practice in a standard syntax easily interpreted by both human and machine.
The associated vFeed.db (The Correlated Vulnerability and Threat Database) is a detective and preventive security information repository useful for gathering vulnerability and mitigation data from scattered internet sources into an unified database.
vFeed’s documentation is now well populated in its Github wiki, and should be read in its entirety:

1. vFeed Framework (API & Correlated Vulnerability Database)
2. Usage (API and Command Line)
3. Methods list
4. vFeed Database Update Calendar

vFeed features include:

• Easy integration within security labs and other pentesting frameworks 
• Easily invoked via API calls from your software, scripts or from command-line. A proof of concept python api_calls.py is provided for this purpose
• Simplify the extraction of related CVE attributes
• Enable researchers to conduct vulnerability surveys (tracking vulnerability trends regarding a specific CPE)
• Help penetration testers analyze CVEs and gather extra metadata to help shape attack vectors to exploit vulnerabilities
• Assist security auditors in reporting accurate information about findings during assignments. vFeed is useful in describing a vulnerability with attributes based on standards and third-party references(vendors or companies involved in the standardization effort)

For reference material…

from lib.core.methods.ref import CveRef

cve = “CVE-2008-0793”

ref = CveRef(cve).get_refs()

print ref

I thought I’d get started on a user interface for vFeed using R and Shiny, appropriately name vFeed Viewer and found on Github here. This first version does not allow direct queries of the vFeed database as I’m working on SQL injection prevention, but it does allow very granular filtering of key vFeed tables. Once I work out safe queries and sanitization, I’ll build the same full correlation features you enjoy from NJ’s Python vFeed client.
You’ll need a bit of familiarity with R to make use of this viewer.
First install R, and RStudio.  From the RStudio console, to ensure all dependencies are met, run install.packages(c(“shinydashboard”,”RSQLite”,”ggplot2″,”reshape2″)).
Download and install the vFeed Viewer in the root vFeed directory such that app.R and the www directory are side by side with vfeedcli.py, etc. This ensures that it can read vfeed.db as the viewer calls it directly with dbConnect and dbReadTable, part of the RSQLite package.
Open app.R with RStudio then, click the Run App button. Alternatively, from the command-line, assuming R is in your path, you can run R -e “shiny::runApp(‘~/shinyapp’)” where ~/shinyapp is the path to where app.R resides. In my case, on Windows, I ran R -e “shiny::runApp(‘c:\\tools\\vfeed\\app.R’)”. Then browser to the localhost address Shiny is listening on. You’ll probably find the RStudio process easier and faster.
One important note about R, it’s not known for performance, and this app takes about thirty seconds to load. If you use Microsoft (Revolution) R with the MKL library, you can take advantage of multiple cores, but be patient, it all runs in memory. Its fast as heck once it’s loaded though.
The UI is simple, including an overview.

At present, I’ve incorporated NVD and CWE search mechanisms that allow very granular filtering.

 As an example, using our favorite CVE-2008-0793, we can zoom in via the search field or the CVE ID drop down menu. Results are returned instantly from 76,123 total NVD entries at present.

From the CWE search you can opt to filter by keywords, such as XSS for this scenario, to find related entries. If you drop cross-site scripting in the search field, you can then filter further via the cwetitle filter field at the bottom of the UI. This is universal to this use of Shiny, and allows really granular results.

You can also get an idea of the number of vFeed entries per vulnerability category entities. I did drop CPEs as their number throws the chart off terribly and results in a bad visualization.

I’ll keep working on the vFeed Viewer so it becomes more useful and helps serve the vFeed community. It’s definitely a work in progress but I feel as if there’s some potential here.

Conslusion

Thanks to NJ for vFeed and all his work with the infosec tools community, if you’re going to Black Hat be certain to stop by Arsenal. Make use of vFeed as part of your vulnerability management practice and remember to check for updates regularly. It’s a great tool, and getting better all the time.
Ping me via email or Twitter if you have questions (russ at holisticinfosec dot org or @holisticinfosec).
Cheers…until next month.

Acknowledgements

Nabil (NJ) Ouchn (@toolswatch)

Continue reading toolsmith #116: vFeed & vFeed Viewer→