This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP Web Malware Scanner Project"

From OWASP
Jump to: navigation, search
(Feedback)
 
(31 intermediate revisions by 2 users not shown)
Line 6: Line 6:
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
  
==OWASP Tool Project Template==
+
==OWASP Web Malware Scanner Tool Project==
  
The OWASP Web Malware Scanner is a malware scanner for web applications. The goal is to be able to scan a web application folder for any malware using a community driven signature database. The Web Malware Scanner is run locally to the web application folder much like an anti-virus. This project was created because the ClamAV project and other similar open source tools were unable to detect some infected files on some of our production servers and we needed a solution to scan our web applications with better results.
+
The OWASP Web Malware Scanner is a malware scanner for web applications. The goal is to be able to scan a web application using a community driven signature database. The Web Malware Scanner works by scanning each files of the web application for known malwares.
 +
 
 +
The Web Malware Scanner is not a vulnerability scanner, it is a malware scanner used to identify compromised web application installations.
  
 
The deliverable is a python application.
 
The deliverable is a python application.
Line 16: Line 18:
 
Web Malware Scanner is a simple malware scanner for web applications. It can be used to identify compromised Wordpress, Joomla and other popular web application installations.
 
Web Malware Scanner is a simple malware scanner for web applications. It can be used to identify compromised Wordpress, Joomla and other popular web application installations.
  
The Web Malware Scanner must be run locally to the web application installation folder. It will scan each files and compare them to the Web Malware Scanner's signature database. Each file is scanned for any known malware MD5 checksum and also for any regular expression based malware signatures.
+
The Web Malware Scanner will scan each files and compare them to the Web Malware Scanner's signature database. Each file is scanned for any known malware MD5 checksum and also for any malware patterns using YARA rules. Finally, the scan will look for insecure permissions for every files and folders.
  
The Web Malware Scanner Project uses regular expressions to search files for malware signatures as opposed to the custom ClamAV signature database wildcard syntax, which is somewhat more limited.  
+
The goal of the OWASP Web Malware Scanner Project is to have a community driven signature database. You are more than welcome to contribute to this project by sending us new malware signatures.
  
The ClamAV custom wildcard syntax only includes the following wildcards: <nowiki>?? Matches any byte. * Matches any number of bytes (including 0 byte). {n} Matches n bytes. {-n} Matches n bytes or less. {n-} Matches at least n bytes. {m-n} Matches between m and n bytes. (0a|1b) Matches 0a or 1b.</nowiki>
+
==Features==
  
The Web Malware Scanner project uses standard regular expressions for a much wider range of matching patterns.
+
* Support for Windows, Linux and MacOS
 +
* Over 500 000 malware MD5 hashes
 +
* Over 500 YARA ruleset databases
  
The default signature database is taken in parts from ClamAV's signature database, SaneSecurity's signature database and other sources.
+
==Downloads==
  
The goal of the OWASP Web Malware Scanner Project is to have a community driven signature database. You are more than welcome to contribute to this project by sending us new malware signatures.
+
'''Windows''': [https://github.com/maxlabelle/WebMalwareScanner Get it from github]
 +
 
 +
'''Linux''': [https://github.com/maxlabelle/WebMalwareScanner Get it from github]
 +
 
 +
'''Mac OS''': [https://github.com/maxlabelle/WebMalwareScanner Get it from github]
  
 
==Licensing==
 
==Licensing==
Line 40: Line 48:
 
[https://github.com/maxlabelle/WebMalwareScanner Source Code]
 
[https://github.com/maxlabelle/WebMalwareScanner Source Code]
  
[https://github.com/maxlabelle/WebMalwareScanner Documentation]
+
[https://github.com/maxlabelle/WebMalwareScanner/wiki Documentation]
  
 
[https://github.com/maxlabelle/WebMalwareScanner/issues Issue Tracker]
 
[https://github.com/maxlabelle/WebMalwareScanner/issues Issue Tracker]
Line 65: Line 73:
  
 
== News and Events ==
 
== News and Events ==
 +
 +
* [01 Jun 2016] Working on version 1.0; New GUI, Automatic updates, new signature database, Standalone application for Windows, Linux and MacOS
  
 
* [04 Mar 2016] The Web Malware Scanner is now an official OWASP Project
 
* [04 Mar 2016] The Web Malware Scanner is now an official OWASP Project
Line 74: Line 84:
 
==How can I participate in your project?==
 
==How can I participate in your project?==
 
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.
 
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.
 +
 +
==I'm not a programmer, how can I help?==
 +
One thing you can do, if you want to help, is to send infected or suspicious files to the project leader. These files will be analysed and added to the signature database if needed.
  
 
= Acknowledgements =
 
= Acknowledgements =
Line 93: Line 106:
 
* Optimize the codebase
 
* Optimize the codebase
 
* Incorporate new ideas and security assessments
 
* Incorporate new ideas and security assessments
 +
* Add scan for compressed files
 +
* Report false positives
 +
* Automatic updates
 
</strong>
 
</strong>
  
Line 116: Line 132:
  
 
=Minimum Viable Product=
 
=Minimum Viable Product=
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<span style="color:#ff0000">
 
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.
 
Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap.  And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category. 
 
</span>
 
 
The Tool Project Template must specify the minimum set of tabs a project should have, provide some an example layout on each tab, provide instructional text on how a project leader should modify the tab, and give some example text that illustrates how to create an actual project.
 
 
It would also be ideal if the sample text was translated into different languages.
 
 
=Project About=
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<span style="color:#ff0000">
 
This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager.
 
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
 
</span>
 
  
{{:Projects/OWASP_Example_Project_About_Page}}
+
We feel that the signature database is the most important aspect of this project. If the database is updated often with new signatures, this project will remain useful.
  
 
__NOTOC__ <headertabs />  
 
__NOTOC__ <headertabs />  
  
 
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Tool]]
 
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Tool]]

Latest revision as of 15:24, 31 December 2016

OWASP Project Header.jpg

OWASP Web Malware Scanner Tool Project

The OWASP Web Malware Scanner is a malware scanner for web applications. The goal is to be able to scan a web application using a community driven signature database. The Web Malware Scanner works by scanning each files of the web application for known malwares.

The Web Malware Scanner is not a vulnerability scanner, it is a malware scanner used to identify compromised web application installations.

The deliverable is a python application.

Description

Web Malware Scanner is a simple malware scanner for web applications. It can be used to identify compromised Wordpress, Joomla and other popular web application installations.

The Web Malware Scanner will scan each files and compare them to the Web Malware Scanner's signature database. Each file is scanned for any known malware MD5 checksum and also for any malware patterns using YARA rules. Finally, the scan will look for insecure permissions for every files and folders.

The goal of the OWASP Web Malware Scanner Project is to have a community driven signature database. You are more than welcome to contribute to this project by sending us new malware signatures.

Features

  • Support for Windows, Linux and MacOS
  • Over 500 000 malware MD5 hashes
  • Over 500 YARA ruleset databases

Downloads

Windows: Get it from github

Linux: Get it from github

Mac OS: Get it from github

Licensing

The Web Malware Scanner Project is released under the BSD 4-clause "Original" or "Old" License.

Project Resources

https://github.com/maxlabelle/WebMalwareScanner

Source Code

Documentation

Issue Tracker

Project Leader

Maxime Labelle ( [email protected] )

Classifications

Project Type Files TOOL.jpg
Incubator Project Owasp-builders-small.png
Owasp-defenders-small.png
Affero General Public License 3.0

News and Events

  • [01 Jun 2016] Working on version 1.0; New GUI, Automatic updates, new signature database, Standalone application for Windows, Linux and MacOS
  • [04 Mar 2016] The Web Malware Scanner is now an official OWASP Project

How can I participate in your project?

All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

I'm not a programmer, how can I help?

One thing you can do, if you want to help, is to send infected or suspicious files to the project leader. These files will be analysed and added to the signature database if needed.

Contributors

The first contributors to the project were:

Roadmap

The base application is already completed. The next step is to populate the signature database and optimize the current codebase.

As of March, 2016, the highest priorities for the next 6 months are:

  • Populate the signature database
  • Optimize the codebase
  • Incorporate new ideas and security assessments
  • Add scan for compressed files
  • Report false positives
  • Automatic updates

Getting Involved

Involvement in the development and promotion of Web Malware Scanner Project is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows:

Coding

We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests

Testing

Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.

Feedback

Please send us feedback about:

  • What do like?
  • What don't you like?
  • What features would you like to see prioritized on the roadmap?
  • Do you think we forgot something important? Let us know!

We feel that the signature database is the most important aspect of this project. If the database is updated often with new signatures, this project will remain useful.