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 ZSC Tool Project"

From OWASP
Jump to: navigation, search
(→‎Road Map and Getting Involved)
(Updating)
Line 7: Line 7:
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
==OWASP ZSC Tool Project==
−
<span style="color:#ff0000">
+
====What is OWASP ZSC ?====
−
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.
 
−
</span>
 
  
−
==ZSC Tool Project==
+
'''OWASP ZSC''' is an open source software in python language which lets you generate customized shellcodes for listed operation systems. This software could be run on Linux under python 2.7.x.  
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
This is where you need to add your more robust project description. A project description should outline the purpose of the project, 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, and project leaders should ensure that the description is meaningful.
 
−
</span>
 
  
 
==Description==
 
==Description==
−
My project at this time is a bunch of python source codes and installer, with pdf documents and html user guide
+
====Usage of shellcodes====
−
I'm already made project and I want to develop it under OWASP Brand, this project is a shellcode generator with have many encryption [user manual and random] with will make it so success.
 
−
project details with description: http://zsc.z3r0d4y.com/
 
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
Shellcodesare small codes in assembly which could be use as the payload in software exploiting. Other usages are in malwares, bypassing antiviruses, obfuscated codes and etc.  
−
<span style="color:#ff0000">
 
−
This section must include a shorter description of what the project is, why the project was started, and what security issue is being helped by the project deliverable. This description will be used to promote the project so make sure the description represents your project in the best way possible.  
 
−
</span>
 
  
−
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]
+
====Why use OWASP ZSC ?====
−
'''
 
  
−
Over the course of my career, I have come across and collected a number of security ''aphorisms.'' These aphorisms constitute the fundamental principles of information security.
+
According to other shellcode generators same as metasploit tools and etc, OWASP ZSC using new encodes and methods which antiviruses won't detect.
 +
OWASP ZSC encoderes are able to generate shellcodes with '''random encodes''' and that's lets you to get '''thousands new dynamic shellcodes''' with same job in just a second,that means you will not get a same code if you use random encodes with same commands, And that make OWASP ZSC one of the bests! otherwise it's gonna generate shellcodes for many operation systems in next versions.  
  
−
None of the ideas or truths are mine, and unfortunately, I did not collect the citations. Initially, I would like to identify the correct citations for each aphorism.
+
==Licensing==
  
−
Additionally, many are re-statements of the same idea; thus, the 'collection of ideas' defines a fundamental principle. As such, I would also like to reverse engineer the principles from the aphorisms where appropriate, as well.
+
====GNU GENERAL PUBLIC LICENSE , Version 3, 29 June 2007====
  
−
==Licensing==
+
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/Ali-Razmjoo/ZCR-Shellcoder/blob/master/LICENSE.md Click to see the full licensing]
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<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.
 
−
</span>
 
  
 
'''The OWASP Security Principles are free to use. In fact it is encouraged!!!
 
'''The OWASP Security Principles are free to use. In fact it is encouraged!!!
Line 54: Line 38:
  
 
== What is OWASP Security Principles Project? ==
 
== What is OWASP Security Principles Project? ==
−
 
+
With using '''OWASP ZSC''' you would be able to generate any customized '''Shellcode''' in your mind including encodes in some seconds. <span style="color:#ff0000">goals ...</span>
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
Here you should add a short description of what your project actually does. What is the primary goal of your project, and why is it important?
 
−
</span>
 
  
 
The end goal is to identify, cite, and document the fundamental principles of information security. Once this is well organised, I think it would be great to publish this through the [http://scriptogr.am/dennis-groves/post/owasp-press OWASP Press]. Of course, it will always remain freely available, and any money collected will go directly into the project to absorb costs with any remaining funds going to the OWASP Foundation.
 
The end goal is to identify, cite, and document the fundamental principles of information security. Once this is well organised, I think it would be great to publish this through the [http://scriptogr.am/dennis-groves/post/owasp-press OWASP Press]. Of course, it will always remain freely available, and any money collected will go directly into the project to absorb costs with any remaining funds going to the OWASP Foundation.
Line 76: Line 56:
 
== Project Leader ==
 
== Project Leader ==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [https://www.owasp.org/index.php/User:Ali_Razmjoo Ali Razmjoo]
−
<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.
 
−
</span>
 
  
 
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
 
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
Line 85: Line 62:
  
 
== Related Projects ==
 
== Related Projects ==
−
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
This is where you can link to other OWASP Projects that are similar to yours.
 
−
</span>
 
  
 
* [[OWASP_CISO_Survey]]
 
* [[OWASP_CISO_Survey]]
Line 101: Line 73:
  
 
== Quick Download ==
 
== Quick Download ==
−
 
+
[https://github.com/Ali-Razmjoo/ZCR-Shellcoder/ Github Page.]
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
[http://zsc.z3r0d4y.com/download/ Download Page.]
−
<span style="color:#ff0000">
 
−
This is where you can link to your repository.
 
−
</span>
 
  
 
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.
 
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.
  
 
However, if you like you may also download the master repository from the following links:
 
However, if you like you may also download the master repository from the following links:
−
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]
+
* [https://github.com/Ali-Razmjoo/ZCR-Shellcoder/zipball/master .zip file.]
−
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]
+
* [https://github.com/Ali-Razmjoo/ZCR-Shellcoder/tarball/master .tgz file.]
  
 
== News and Events ==
 
== News and Events ==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [28 July 2015] [http://zsc.z3r0d4y.com/ OWASP ZSC Version 1.0.5.1 Released!]
−
<span style="color:#ff0000">
 
−
This is where you can link to press your project has been a part of. Appropriate press includes: Project Leader interviews, articles written about your project, and videos about your project.  
 
−
</span>
 
−
 
 
−
* [20 Nov 2013] News 2
 
−
* [30 Sep 2013] News 1
 
  
 
== In Print ==
 
== In Print ==
Line 155: Line 118:
 
=FAQs=
 
=FAQs=
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
To see full guides please visit our [http://zsc.z3r0d4y.com/wiki wiki page].
−
<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.'
+
====Help Menu====
−
</span>
+
<pre><nowiki>
 +
Switches:
 +
-h, --h, -help, --help => to see this help guide
 +
-os => choose your os to create shellcode
 +
-oslist  => list os for switch -os
 +
-o => output filename
 +
-job => what shellcode gonna do for you ?
 +
-joblist => list of -job switch
 +
-encode => generate shellcode with encode
 +
-types => types of encode for -encode switch
 +
-wizard => wizard mod
 +
 
 +
-update => check for update
 +
-about => about software and developers.</nowiki></pre>
 +
 
  
 
=Requirement / Installation=
 
=Requirement / Installation=
  
−
'''Requirement'''
 
−
Please insert requirements
 
  
 
'''Installation'''
 
'''Installation'''
 +
Go to download page, and download last version in github. Extract and run installer.py, then you are able to run software with OWASP ZSC command or you can directly execute zsc.py without installing it.or you can follow these commands to install the last version:
 +
 +
<pre><nowiki>wget https://github.com/Ali-Razmjoo/ZCR-Shellcoder/archive/master.zip -O zcr-shellcoder.zip && unzip zcr-shellcoder.zip &&
 +
rm -rf zcr-shellcoder.zip && mv ZCR-Shellcoder-master ZCR-Shellcoder && cd ZCR-Shellcoder && python installer.py</nowiki></pre>
 +
 +
 +
http://zsc.z3r0d4y.com/images/Snapshot_2015-07-27_114843.png
 +
 +
 +
'''Note''': Software could be '''uninstall''' with executing '''uninstaller.py'''
 +
 +
'''Note''': Software installation directory is "'''/usr/share/zcr-shellcoder'''"
  
−
*Download please insert the github link: https://github.com
 
−
*Sample And run
 
  
 
==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.
+
===Be an OWASP ZSC developer===
  
−
==If I am not a programmer can I participate in your project?==
+
To join us for developing ZCR Shellcoder, you may need to know Assembly, Shellcoding, Python. Then check up this [http://zsc.z3r0d4y.com/table.html Table] and build a shellcode generator with python which we didn’t made it yet, then send it to us and after checking and testing your code, You will became an OWASP ZSC developer and your code will add to software in next versions.
−
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.  
+
 
 +
Also please visit [http://zsc.z3r0d4y.com/developers/ Developer Pages.]
 +
 
 +
http://zsc.z3r0d4y.com/images/Snapshot_2015-07-27_135930.png
  
 
= Acknowledgements =
 
= Acknowledgements =
  
 
==Contributors==
 
==Contributors==
−
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<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 Security Principles project 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].  
 
The OWASP Security Principles project 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].  
Line 194: Line 175:
 
* [https://github.com/sublimino Andrew Martin]
 
* [https://github.com/sublimino Andrew Martin]
 
* [https://github.com/Lambdanaut Josh Thomas]
 
* [https://github.com/Lambdanaut Josh Thomas]
−
* '''YOUR NAME BELONGS HERE'''
+
* [https://www.owasp.org/index.php/User:Ali_Razmjoo Ali Razmjoo]
  
 
= Road Map and Getting Involved =
 
= Road Map and Getting Involved =
 
As I said before, I started project some month ago without OWASP Brand, and More project details is available on website : http://zsc.z3r0d4y.com/
 
As I said before, I started project some month ago without OWASP Brand, and More project details is available on website : http://zsc.z3r0d4y.com/
  
−
What is ZSC ?
+
What is OWASP ZSC ?
 
ZeroDay Cyber Research Shellcoder [Generator] is an open source software in python language which lets you generate customized shellcodes for listed operation systems. This software can be run on Linux under python 2.7.x.  
 
ZeroDay Cyber Research Shellcoder [Generator] is an open source software in python language which lets you generate customized shellcodes for listed operation systems. This software can be run on Linux under python 2.7.x.  
  
Line 205: Line 186:
 
Shellcodesare small codes in assembly which could be use as the payload in software exploiting. Other usages are in malwares, bypassing antiviruses, obfuscated codes and etc.  
 
Shellcodesare small codes in assembly which could be use as the payload in software exploiting. Other usages are in malwares, bypassing antiviruses, obfuscated codes and etc.  
  
−
Why use ZSC ?
+
Why use OWASP ZSC ?
−
According to other shellcode generators same as metasploit tools and etc, ZSC using new encodes and methods which antiviruses won't detect.
+
According to other shellcode generators same as metasploit tools and etc, OWASP ZSC using new encodes and methods which antiviruses won't detect.
−
ZSC encoderes are able to generate shellcodes with random encodes and that's lets you to get thousands new dynamic shellcodes with same job in just a second,that means you will not get a same code if you use random encodes with same commands, And that make ZSC one of the bests! otherwise it's gonna generate shellcodes for many operation systems in next versions.  
+
OWASP ZSC encoderes are able to generate shellcodes with random encodes and that's lets you to get thousands new dynamic shellcodes with same job in just a second,that means you will not get a same code if you use random encodes with same commands, And that make OWASP ZSC one of the bests! otherwise it's gonna generate shellcodes for many operation systems in next versions.  
  
 
Project features: http://zsc.z3r0d4y.com/table.html
 
Project features: http://zsc.z3r0d4y.com/table.html

Revision as of 06:32, 5 August 2015

OWASP Project Header.jpg

OWASP ZSC Tool Project

What is OWASP ZSC ?

OWASP ZSC is an open source software in python language which lets you generate customized shellcodes for listed operation systems. This software could be run on Linux under python 2.7.x.

Description

Usage of shellcodes

Shellcodesare small codes in assembly which could be use as the payload in software exploiting. Other usages are in malwares, bypassing antiviruses, obfuscated codes and etc.

Why use OWASP ZSC ?

According to other shellcode generators same as metasploit tools and etc, OWASP ZSC using new encodes and methods which antiviruses won't detect. OWASP ZSC encoderes are able to generate shellcodes with random encodes and that's lets you to get thousands new dynamic shellcodes with same job in just a second,that means you will not get a same code if you use random encodes with same commands, And that make OWASP ZSC one of the bests! otherwise it's gonna generate shellcodes for many operation systems in next versions.

Licensing

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 licensing


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.

What is OWASP Security Principles Project?

With using OWASP ZSC you would be able to generate any customized Shellcode in your mind including encodes in some seconds. goals ...

The end goal is to identify, cite, and document the fundamental principles of information security. Once this is well organised, I think it would be great to publish this through the OWASP Press. Of course, it will always remain freely available, and any money collected will go directly into the project to absorb costs with any remaining funds going to the OWASP Foundation.

This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.

Presentation

This is where you can link to slide presentations related to your project.


AppSec USA 2013 [1]

Project Leader


Related Projects

Openhub

Quick Download

Github Page. Download Page.

The home of the OWASP Security Principles is on GitHub. You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.

However, if you like you may also download the master repository from the following links:

News and Events

In Print

This is where you place links to where your project product can be downloaded or purchased, in the case of a book.

This project can be purchased as a print on demand book from Lulu.com

Classifications

Here is where you can let the community know what project stage your project is currently in, whether the project is a builder, breaker, or defender project, and what type of project you are running.

New projects.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg
Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_ZSC_Tool_Project&oldid=198427"