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 VBScan Project"

From OWASP
Jump to: navigation, search
(→‎News and Events)
 
(120 intermediate revisions by 3 users not shown)
Line 5: Line 5:
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 +
[[file:VBScan_Logo.png|right]]
  
−
<span style="color:#ff0000">
+
<div class="plainlinks">
−
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.
+
'''Share this:'''&nbsp;
−
</span>
+
<span title="Share via e-mail" class="plainlinks">[[File:social-email.png|E-mail this story|link=mailto:?subject={{FULLPAGENAMEE}}&body={{FULLPAGENAMEE}}:%0A{{fullurle:{{FULLPAGENAME}}}}]]</span>
 +
<span title="Share on Facebook">[[File:social-facebook.png|Bookmark with Facebook|link=http://www.facebook.com/sharer.php?u={{fullurle:{{FULLPAGENAME}}}}&t={{urlencode:{{FULLPAGENAME}}}}]]</span>
 +
<span  title="Share on Digg">[[File:social-digg.png|Share on Digg.com|link=http://digg.com/submit?url={{fullurle:{{FULLPAGENAME}}}}&title={{urlencode:{{FULLPAGENAME}} }}]]</span>
 +
<span  title="Share on delicious">[[File:social-delicious.png|16px|Share on delicious|link=http://delicious.com/post?url={{fullurle:{{FULLPAGENAME}}}}&title={{urlencode:{{FULLPAGENAME}}}}]]</span>
 +
<span  title="Share on reddit">[[File:social-reddit.png|Share on reddit.com|link=http://reddit.com/submit?url={{fullurle:{{FULLPAGENAME}}}}&title={{urlencode:{{FULLPAGENAME}}}}]]</span>
 +
<span  title="Share on StumbleUpon">[[File:social-stumbleupon.png|16px|Share on stumbleupon.com|link=http://stumbleupon.com/submit?url={{fullurle:{{FULLPAGENAME}}}}&title={{urlencode:{{FULLPAGENAME}}}}]]</span>
 +
<span  title="Share on LinkedIn">[[File:social-linkedin.png|16px|Share on LinkedIn.com|link=http://www.linkedin.com/shareArticle?mini=true&url={{fullurle:{{FULLPAGENAME}}}}&title={{urlencode:{{FULLPAGENAME}}}}]]</span>
 +
<span title="Share on Twitter">[[File:social-twitter.png|alt=Share on twitter.com|link=http://twitter.com/?status={{fullurle:{{FULLPAGENAME}}}}|Share on twitter.com]]</span>
 +
<span title="Seed on Newsvine">[[File:social-newsvine.png|16px|Seed on Newsvine|link=http://www.newsvine.com/_wine/save?popoff=1&u={{fullurle:{{FULLPAGENAME}}}}]]</span>
 +
</div>
 +
 
 +
[[File:joomscan_download.png|link=https://github.com/rezasp/vbscan/releases]]
 +
 
 +
==OWASP VBScan Project ==
 +
OWASP VBScan (short for [VB]ulletin Vulnerability [Scan]ner) is an opensource project in perl programming language to detect VBulletin CMS vulnerabilities and analyses them.
 +
 
 +
 
 +
==== Why VBScan ? ====
 +
 
 +
If you want to do a penetration test on a vBulletin Forum, VBScan is Your best shot ever! This Project is being faster than ever and updated with the latest VBulletin vulnerabilities.
 +
 
 +
[[File:vbscan_screenshot.jpg]]
  
−
==OWASP VBScan Tool Project ==
 
−
<span style="color:#ff0000">
 
  
−
This project is already written in perl language and have many users which you can see more information in here https://github.com/rezasp/vbscan
+
==== Popularity ====
  
−
This 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.
+
* ToolsWatch Annual Best Free/Open Source Security Tool Survey:
−
</span>
+
** 2016 [http://www.toolswatch.org/2017/02/2016-top-security-tools-as-voted-by-toolswatch-org-readers/ 3rd]
  
−
The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.
 
  
 
==Description==
 
==Description==
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
−
VBScan is an opensource project in perl programming language to detect VBulletin CMS vulnerabilities and analyses them.This Project is being faster than ever and updated with the latest VBulletin vulnerabilities.
 
  
−
This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful.
+
OWASP VBScan (short for [VB]ulletin Vulnerability [Scan]ner) is an opensource project in perl programming language to detect VBulletin CMS vulnerabilities and analyses them.
−
</span>
 
  
−
The Tool Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Tool project.  After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red.  Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category.  The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.
 
  
−
Creating a new set of project pages from scratch can be a challenging task.  By providing a sample layout, with instructional text and examples, the OWASP Tool Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.
 
  
−
==Licensing==
+
{|
−
<span style="color:#ff0000">
+
|-
−
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses 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.
+
{{#ev:youtube|NGEtJoGL2yA}}&nbsp;
−
</span>
+
{{#ev:youtube|SirozqDYERA}}
 +
|}
 +
 
 +
==LICENSE==
  
−
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html 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 &copy; by {the Project Leader(s) or OWASP} {Year(s)}. 
+
====GNU GENERAL PUBLIC LICENSE , Version 3, 29 June 2007====
  
−
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
+
Copyright (C) 2007 Free Software Foundation, Inc. http://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [https://github.com/rezasp/vbscan/blob/master/COPYING.GPL Click to see the full license]
  
−
== Project Resources ==
 
−
<span style="color:#ff0000">
 
−
This 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.
 
−
</span>
 
  
−
[https://github.com/SamanthaGroves Installation Package]
+
'''The OWASP Security Principles are free to use. In fact it is encouraged!!!
 +
'' Additionally, I also encourage you to contribute back to the project. I have no monopoly on this knowledge; however, we all have pieces of this knowledge from our experience. Let's begin by putting our individual pieces together to make something great. Great things happen when people work together.
  
−
[https://github.com/SamanthaGroves Source Code]
+
The OWASP Security Principles are licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
  
−
[https://github.com/SamanthaGroves What's New (Revision History)]
+
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 +
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
  
−
[https://github.com/SamanthaGroves Documentation]
+
== Quick Download ==
 +
[https://github.com/rezasp/vbscan Github Page.]
  
−
[https://github.com/SamanthaGroves Wiki Home Page]
+
[Download Page.]
  
−
[https://github.com/SamanthaGroves Issue Tracker]
+
* [https://github.com/rezasp/vbscan/zipball/master .zip file.]
 +
* [https://github.com/rezasp/vbscan/tarball/master .tgz file.]
  
−
[https://github.com/SamanthaGroves Slide Presentation]
+
== Project Leader ==
  
−
[https://github.com/SamanthaGroves Video]
 
  
−
== Project Leader ==
+
[mailto:[email protected] Mohammad Reza Espargham]
−
<span style="color:#ff0000">
+
 
−
A 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.
+
== Contributors & Main Developers ==
−
</span>
+
 
  
−
Project leader's name
+
* [https://github.com/TahaDaneshnia Taha Daneshnia]
 +
* [https://github.com/saturn99 saturn99]
  
−
== Related Projects ==
 
−
<span style="color:#ff0000">
 
−
This is where you can link to other OWASP Projects that are similar to yours.
 
−
</span>
 
−
* [[OWASP_Code_Project_Template]]
 
−
* [[OWASP_Documentation_Project_Template]]
 
  
 
==Classifications==
 
==Classifications==
Line 92: Line 104:
  
 
== News and Events ==
 
== News and Events ==
−
<span style="color:#ff0000">
 
−
This 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.
 
−
</span>
 
−
* [12 Feb 2013] Support for Spanish is now available with this release.
 
−
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!
 
−
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.
 
−
* [20 Nov 2013] 1.0 Beta 2 Release is available for download. This release offers several bug fixes, a few performance improvements, and addressed all outstanding issues from a security audit of the code.
 
−
* [30 Sep 2013] 1.0 Beta 1 Release is available for download.  This release offers the first version with all of the functionality for a minimum viable product.   
 
  
 +
* VBScan 0.1.8 - "Self Challenge" Released
 +
* OWASP VBScan was introduced in OFFSECONF 2017
 +
* [http://www.toolswatch.org/2017/02/2016-top-security-tools-as-voted-by-toolswatch-org-readers/ OWAPS VBScan came third in the Top Security Tools of 2016 as voted by ToolsWatch.org readers]
 +
* VBScan 0.1.7.1 - "Larry Wall" Released
 +
* VBScan 0.1.7 - "Larry Wall" Released
 +
* OWASP VBScan has been selected for BSides/BlackHat USA 2016
 +
* VBScan 0.1.6 - "Dennis Ritchie again" Released
 +
* VBScan 0.1.5 - "Dennis Ritchie" Released
 
|}
 
|}
−
 
−
=FAQs=
 
−
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'
 
−
</span>
 
−
 
−
==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.
 
−
 
−
==If I am not a programmer can I participate in your project?==
 
−
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.  See the Road Map and Getting Involved tab for more details.
 
  
 
= Acknowledgements =
 
= Acknowledgements =
 
==Contributors==
 
==Contributors==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
VBScan source code located in github and you could see contributors in this [https://github.com/rezasp/vbscan/graphs/contributors URL].
−
<span style="color:#ff0000">
 
−
The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project.
 
−
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project.  
 
−
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
 
−
</span>
 
  
−
The OWASP Tool Project Template is developed by a worldwide team of volunteers. A live update of project  [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].  
+
Please feel free to fork and submit your pull request to develop VBScan Project together.
  
−
The first contributors to the project were:
+
==Leader==
  
−
* [https://www.owasp.org/index.php/User:Clerkendweller Colin Watson] who created the OWASP Cornucopia project that the template was derived from
+
* [https://www.owasp.org/index.php/User:rezasp Mohammad Reza Espargham]
−
* [https://www.owasp.org/index.php/User:Chuck_Cooper Chuck Cooper] who edited the template to convert it from a documentation project to a Tool Project Template
 
−
* '''YOUR NAME BELONGS HERE AND YOU SHOULD REMOVE THE PRIOR 3 NAMES'''
 
  
 
= Road Map and Getting Involved =
 
= Road Map and Getting Involved =
−
This project is going to be the best VBulletin scanner, it could be handle in ZAP and/or get develop to a single scanner, At the end We could have a forum cms penetration tester which is updated with the last vulnerabilities.
+
This project is going to be the best VBulletin scanner, At the end We could have a forum cms penetration tester which is updated with the last vulnerabilities.
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
==Roadmap==
−
<span style="color:#ff0000">
 
−
A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.
 
−
Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.
 
−
</span>
 
  
−
==Roadmap==
+
This Project was created to be a VBScanner which already it is and now need to be best with some tasks:
−
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
 
−
<strong>
 
−
* Complete the first draft of the Tool Project Template
 
−
* Get other people to review the Tool Project Template and provide feedback
 
−
* Incorporate feedback into changes in the Tool Project Template
 
−
* Finalize the Tool Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
 
−
</strong>
 
  
−
Subsequent Releases will add
+
* Optimize software core to be fast and easy to develop
−
<strong>
+
* make it module base and create libraries for developers
−
* Internationalization Support
+
* Support all OS
−
* Additional Unit Tests
+
* Be update with latest exploits.
−
* Automated Regression tests
+
* Create documents for newbie users
−
</strong>
+
* Keep testing and fix bugs!
  
−
==Getting Involved==
 
−
Involvement in the development and promotion of <strong>Tool Project Template</strong> 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
 
−
===Localization===
 
−
Are you fluent in another language? Can you help translate the text strings in the <strong>Tool Project Template</strong> into that language?
 
−
===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===
 
===Feedback===
−
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:
+
Please submit your feedbacks and issues in [https://github.com/rezasp/vbscan/issues HERE].
 
<ul>
 
<ul>
 
<li>What do like?</li>
 
<li>What do like?</li>
 
<li>What don't you like?</li>
 
<li>What don't you like?</li>
 
<li>What features would you like to see prioritized on the roadmap?</li>
 
<li>What features would you like to see prioritized on the roadmap?</li>
 +
<li>Do you have any problem with tool?</li>
 +
<li>Do you need any exploit to be add?</li>
 
</ul>
 
</ul>
  
 
=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.
+
VBScan Could be improved by adding more module and fixing core to make a better and faster threads, right now VBScan is including more than 70 modules to check bugs, vulnerabilities in perl language. To be more update and check exploits please check the [https://github.com/rezasp/vbscan github page].
 +
 
 +
=Project About=
 +
 
 +
 
 +
{{:Projects/OWASP_VBScan_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}}
 
  
 +
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
__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_Document]] [[Category:OWASP_Tool]] [[Category:OWASP_Download]]

Latest revision as of 20:00, 17 September 2018

OWASP Project Header.jpg
VBScan Logo.png

Share this:  E-mail this story Bookmark with Facebook Share on Digg.com Share on delicious Share on reddit.com Share on stumbleupon.com Share on LinkedIn.com Share on twitter.com Seed on Newsvine

Joomscan download.png

OWASP VBScan Project

OWASP VBScan (short for [VB]ulletin Vulnerability [Scan]ner) is an opensource project in perl programming language to detect VBulletin CMS vulnerabilities and analyses them.


Why VBScan ?

If you want to do a penetration test on a vBulletin Forum, VBScan is Your best shot ever! This Project is being faster than ever and updated with the latest VBulletin vulnerabilities.

Vbscan screenshot.jpg


Popularity

  • ToolsWatch Annual Best Free/Open Source Security Tool Survey:


Description

OWASP VBScan (short for [VB]ulletin Vulnerability [Scan]ner) is an opensource project in perl programming language to detect VBulletin CMS vulnerabilities and analyses them.


 

LICENSE

GNU GENERAL PUBLIC LICENSE , Version 3, 29 June 2007

Copyright (C) 2007 Free Software Foundation, Inc. http://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Click to see the full license


The OWASP Security Principles are free to use. In fact it is encouraged!!! Additionally, I also encourage you to contribute back to the project. I have no monopoly on this knowledge; however, we all have pieces of this knowledge from our experience. Let's begin by putting our individual pieces together to make something great. Great things happen when people work together.

The OWASP Security Principles are licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.

Quick Download

Github Page.

[Download Page.]

Project Leader

Mohammad Reza Espargham

Contributors & Main Developers


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

Contributors

VBScan source code located in github and you could see contributors in this URL.

Please feel free to fork and submit your pull request to develop VBScan Project together.

Leader

This project is going to be the best VBulletin scanner, At the end We could have a forum cms penetration tester which is updated with the last vulnerabilities.

Roadmap

This Project was created to be a VBScanner which already it is and now need to be best with some tasks:

  • Optimize software core to be fast and easy to develop
  • make it module base and create libraries for developers
  • Support all OS
  • Be update with latest exploits.
  • Create documents for newbie users
  • Keep testing and fix bugs!


Feedback

Please submit your feedbacks and issues in HERE.

  • What do like?
  • What don't you like?
  • What features would you like to see prioritized on the roadmap?
  • Do you have any problem with tool?
  • Do you need any exploit to be add?

VBScan Could be improved by adding more module and fixing core to make a better and faster threads, right now VBScan is including more than 70 modules to check bugs, vulnerabilities in perl language. To be more update and check exploits please check the github page.

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_VBScan_Project&oldid=243498"