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"
(→OWASP Tool Project Template) |
(→Description) |
||
| Line 20: | Line 20: | ||
==Description== | ==Description== | ||
| − | |||
| − | |||
| − | |||
| − | Web Malware Scanner is a simple malware scanner for | + | 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 | + | 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 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 ClamAV custom wildcard syntax only includes the following wildcards: | ||
| + | |||
| + | ?? 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. | ||
| + | |||
| + | The Web Malware Scanner project uses standard regular expressions for a much wider range of matching patterns. | ||
| + | |||
| + | The default signature database is taken in parts from ClamAV's signature database, SaneSecurity's signature database and other sources. | ||
| + | |||
| + | 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. | ||
==Licensing== | ==Licensing== | ||
Revision as of 14:42, 4 March 2016
|
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project. OWASP Tool Project TemplateThis section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for. 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 deliverable is a python application. DescriptionWeb 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 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 ClamAV custom wildcard syntax only includes the following wildcards: ?? Matches any 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. The Web Malware Scanner project uses standard regular expressions for a much wider range of matching patterns. The default signature database is taken in parts from ClamAV's signature database, SaneSecurity's signature database and other sources. 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. LicensingA project must be licensed under a community friendly or open source license. For more information on OWASP recommended licenses, please see OWASP Licenses. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects. This example assumes that you want to use the AGPL 3.0 license. Modified BSD, 3-clause License This program is free software: you can redistribute it and/or modify it under the terms of the link GNU Affero General Public License 3.0 as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright © by {the Project Leader(s) or OWASP} {Year(s)}. |
Project ResourcesThis is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. https://github.com/maxlabelle/WebMalwareScanner Project LeaderA project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members. Project leader's name Related ProjectsI am already a project leader of the VaultDB project. This is where you can link to other OWASP Projects that are similar to yours. Classifications
|
News and EventsThis is where you can provide project updates, links to any events like conference presentations, Project Leader interviews, case studies on successful project implementations, and articles written about your project.
| |||||||
