xtawb
Open in Telegram
No data
Subscribers
-324 hours
-197 days
-2430 days
Posts Archive
Resume Options
This option is a really, really nice one that allows you to resume scanning if your previous scan crashed. When we’re dealing with potentially thousands of endpoints, crashes can occur, so this options is a real lifesaver!
--resume ew.db
Path to db file if you want to resume. You can find the database file in the directory (named the current date and time) that EyeWitness automatically creates when running.
Resume Options
This option is a really, really nice one that allows you to resume scanning if your previous scan crashed. When we’re dealing with potentially thousands of endpoints, crashes can occur, so this options is a real lifesaver!
--resume ew.db
Path to db file if you want to resume. You can find the database file in the directory (named the current date and time) that EyeWitness automatically creates when running.
--user-agent User Agent
User Agent to use for all requests.
--difference Difference Threshold
Difference threshold when determining if user agent requests are close “enough” (Default: 50).
--proxy-ip 127.0.0.1
IP of web proxy to go through.
--proxy-port 8080
Port of web proxy to go through.
--proxy-type socks5
Proxy type (socks5/http).
--show-selenium
Show display for selenium.
--resolve
Resolve IP/Hostname for targets.
--add-http-ports ADD_HTTP_PORTS
Comma-separated additional port(s) to assume are http (e.g. ‘8018,8028’).
--add-https-ports ADD_HTTPS_PORTS
Comma-separated additional port(s) to assume are https (e.g. ‘8018,8028’)
--only-ports ONLY_PORTS
Comma-separated list of exclusive ports to use (e.g. ‘80,8080’).
--prepend-https
Prepend http:// and https:// to URLs without either
--selenium-log-path SELENIUM_LOG_PATH
Selenium geckodriver log path
Web Options
These options deal with the way that EyeWitness takes screenshots of the resulting pages. All of this can be configured to handle that HTTP(S) traffic in just the way you want it! Note that some of these options are also required to adhere to some bug bounty program’s rules.
Report Output Options
Couple of minor options to change the output file.
-d Directory Name
Directory name for report output
--results Hosts Per Page
Number of Hosts per page of report
--no-prompt
Don’t prompt to open the report
Timing Options
Need to go fast, need to slow down? These options help you go to town! Please take a close look at these options as they can help you stay within the required limits of bug bounty programs!
--timeout
Timeout Maximum number of seconds to wait while requesting a web page (Default: 7).
--jitter # of Seconds
Randomize URLs and add a random delay between requests.
--delay # of Seconds
Delay between the opening of the navigator and taking the screenshot.
--threads # of Threads
Number of threads to use while using file based input.
--max-retries Max retries on a timeout
Max retries on timeouts.
Input options
These are the options that can help you input the targets to take screenshots of.
-f Filename
Line-separated file containing URLs to capture. As seen in the example above.
-x Filename.xml
Nmap XML or .Nessus file because yes, this tool can parse that output!
--single Single URL
Single URL/Host to capture. If for some reason you’d only want to scan a single target.
--no-dns
Skip DNS resolution when connecting to websites. Can be useful in specific cases if you’re going through a VPN for example.
Now we can execute eyewitness -f domains.txt and this will start the tool.
After executing, the tool will open the result in your browser. Here you can assess the results. Let’s discuss them the screenshot below.
The result page starts off by giving us a nice overlay of all everything that it found. In this case we have Unauthorized pages, Not Found pages and Bad requests already filtered out of all the rest. Nice!
Scrolling down, we find screenshots and the headers of all these pages. We can now quickly assess which page we would like to target first!
you can see, installing EyeWitness consists of 2 steps:
$ Clone the repository: git clone https://github.com/FortyNorthSecurity/EyeWitness.git
$ Run the setup.sh script: sh EyeWitness/Python/setup/setup.sh
That’s all! If all goes well, you’ve now successfully installed EyeWitness!
Now we can execute eyewitness -f domains.txt and this will start the tool.
After executing, the tool will open the result in your browser. Here you can assess the results. Let’s discuss them the screenshot below.
The result page starts off by giving us a nice overlay of all everything that it found. In this case we have Unauthorized pages, Not Found pages and Bad requests already filtered out of all the rest. Nice!
Scrolling down, we find screenshots and the headers of all these pages. We can now quickly assess which page we would like to target first!
you can see, installing EyeWitness consists of 2 steps:
$ Clone the repository: git clone https://github.com/FortyNorthSecurity/EyeWitness.git
$ Run the setup.sh script: sh EyeWitness/Python/setup/setup.sh
That’s all! If all goes well, you’ve now successfully installed EyeWitness!
you can see, installing EyeWitness consists of 2 steps:
$ Clone the repository: git clone https://github.com/FortyNorthSecurity/EyeWitness.git
$ Run the setup.sh script: sh EyeWitness/Python/setup/setup.sh
That’s all! If all goes well, you’ve now successfully installed EyeWitness!
- XSRFProbe
"Comprehensive Security Testing Tool"
XSRFProbe is a powerful tool used for security testing to identify potential penetration vulnerabilities in web applications. The tool relies on Cross-Site Request Forgery (XSRF) attacks that target weaknesses in web applications trusting external requests without verifying their source.
How to Use XSRFProbe:
1. Download XSRFProbe from its official website or from the GitHub repository.
2. Install it in Kali Linux using the following commands:
git clone https://github.com/0xInfection/XSRFProbe.git
cd XSRFProbe
pip3 install -r requirements.txt
3. After installation, you can use XSRFProbe to test web applications by executing the following command:
python3 xsrfprobe.py -u <URL>
What XSRFProbe is Used For:
- XSRFProbe is used to test web applications to detect potential penetration vulnerabilities.
- It can be used to identify unauthorized accessible requests in the application.
Can it be Used in Termux on Mobile Phones?
Yes, XSRFProbe can be used in the Termux application on mobile phones. To download it, follow these steps:
pkg install git
pkg install python
git clone https://github.com/0xInfection/XSRFProbe.git
cd XSRFProbe
pip install -r requirements.txt
-----
- XSRFProbe
XSRFProbe هي أداة قوية تستخدم لاختبار الأمان للتعرف على ثغرات الاختراق المحتملة في تطبيقات الويب. تعتمد الأداة على هجوم Cross-Site Request Forgery (XSRF) الذي يستهدف ضعف في تطبيقات الويب التي تثق بالطلبات الخارجية دون التحقق من مصدرها.
طريقة استخدام XSRFProbe:
1. قم بتحميل XSRFProbe من موقعها الرسمي أو من مخزن GitHub.
2. قم بتثبيتها في نظام Kali Linux باستخدام الأوامر التالية:
git clone https://github.com/0xInfection/XSRFProbe.git
cd XSRFProbe
pip3 install -r requirements.txt
3. بعد التثبيت، يمكنك استخدام XSRFProbe لاختبار التطبيقات الويب عن طريق تنفيذ الأمر التالي:
python3 xsrfprobe.py -u <URL>
فيما تستخدم XSRFProbe:
- تستخدم XSRFProbe لاختبار تطبيقات الويب للكشف عن ثغرات الاختراق المحتملة.
- يمكن استخدامها لتحديد الطلبات التي يمكن الوصول إليها بشكل غير مصرح به في التطبيق.
هل يمكن استخدامها في تطبيق التيرمكس على الهاتف؟
نعم، يمكن استخدام XSRFProbe في تطبيق Termux على الهاتف. لتحميلها، اتبع الخطوات التالية:
pkg install git
pkg install python
git clone https://github.com/0xInfection/XSRFProbe.git
cd XSRFProbe
pip install -r requirements.txtWe are displaying the vulnerabilities.log file which has some crucial information about the scan.
