Hacking Articles Tips Tricks Videos Tutorials
468 subscribers
65.8K photos
15 videos
157 files
132K links
Exploit
Pentesting
Hacking
Red Team
Blue Team
Kali Linux
Bug Bounty
Black Hat
Cyber security etc

@Hacking_Video
@Hacking_attack
Download Telegram
Finding IDORs, the conceptual way

This is my take on IDORs and how to understand them when you are just starting in the Web Application Penetration Testing.Continue reading on Medium »
Read more...
Rdesktop - Open Source Client for Microsoft's RDP protocol

rdesktop is an open source client for Microsoft's RDP protocol. It is known to work with Windows versions ranging from NT 4 Terminal Server to Windows 2012 R2 RDS. rdesktop currently has implemented the RDP version 4 and 5 protocols. Installation rdesktop uses a GNU-style build procedure. Typically all that is necessary to install rdesktop is the following: % ./configure% make% make install The default is to install under /usr/local. This can be changed by adding --prefix= to the configure line. The smart-card support module uses PCSC-lite. You should use PCSC-lite 1.2.9 or later. To enable smart-card support in the rdesktop add --enable-smartcard to the configure line. Note for users building from source If you have retrieved a snapshot of the rdesktop source, you will first need to run ./bootstrap in order to generate the build infrastructure. This is not necessary for release versions of rdesktop. Usage Connect to an RDP server with: % rdesktop server where server is the name of the Terminal Services machine. If you receive "Connection refused", this probably means that the server does not have Terminal Services enabled, or there is a firewall blocking access. You can also specify a number of options on the command line. These are listed in the rdesktop manual page (run man rdesktop). Download Rdesktop
Read more...

___________________________
@hacking_Attack
@Hacking_Video
rdesktop is an open source client for Microsoft's RDP protocol. It is known to work with Windows (https://www.kitploit.com/search/label/Windows) versions ranging from NT 4 Terminal Server to Windows 2012 R2 RDS. rdesktop currently has implemented the RDP version 4 and 5 protocols.
Installation
rdesktop uses a GNU-style build procedure. Typically all that is necessary to install rdesktop is the following: % ./configure
% make
% make install
The default is to install under /usr/local. This can be changed by adding --prefix= to the configure line. The smart-card support module uses PCSC-lite. You should use PCSC-lite 1.2.9 or later. To enable smart-card support in the rdesktop add --enable-smartcard to the configure line.
Note for users building from source
If you have retrieved a snapshot of the rdesktop source, you will first need to run ./bootstrap in order to generate the build infrastructure. This is not necessary for release versions of rdesktop.
Usage
Connect to an RDP server with: % rdesktop server
where server is the name of the Terminal Services machine. If you receive "Connection refused", this probably means that the server does not have Terminal Services enabled, or there is a firewall (https://www.kitploit.com/search/label/Firewall) blocking access. You can also specify a number of options on the command line. These are listed in the rdesktop manual page (run man rdesktop).

Download Rdesktop (https://github.com/rdesktop/rdesktop)

___________________________
@hacking_Attack
@Hacking_Video
Hacking Articles Tips Tricks Videos Tutorials
Photo
KitPloit - PenTest Tools!
Rdesktop - Open Source Client for Microsoft's RDP protocol

https://blogger.googleusercontent.com/img/a/AVvXsEjI9_dtJMGFIo2ekUTFnK-BYMm-b9mDbEawVBsdN3vwWYN07iaWgbErPWsrqVbYJLmUHajMGJiegtxAC-nuy4WhR_2YYeLON4EF-FuX5J8dBpu8c3E3hgNSpehEPhjQLTh37lzaVSK6VtCP2esnZcO09zo4ZMLtOEyTBefOHtkG1Yhpq96sjhL15MNCOQ=w640-h360
rdesktop is an open source client for Microsoft's RDP protocol. It is known to work with Windows versions ranging from NT 4 Terminal Server to Windows 2012 R2 RDS. rdesktop currently has implemented the RDP version 4 and 5 protocols.
Installation

rdesktop uses a GNU-style build procedure. Typically all that is necessary to install rdesktop is the following:

% ./configure
% make
% make install


The default is to install under /usr/local. This can be changed by adding --prefix=to the configure line.

The smart-card support module uses PCSC-lite. You should use PCSC-lite 1.2.9 or later. To enable smart-card support in the rdesktop add --enable-smartcardto the configure line.

Note for users building from source

If you have retrieved a snapshot of the rdesktop source, you will first need to run ./bootstrapin order to generate the build infrastructure. This is not necessary for release versions of rdesktop.

Usage

Connect to an RDP server with:

% rdesktop server


where serveris the name of the Terminal Services machine. If you receive "Connection refused", this probably means that the server does not have Terminal Services enabled, or there is a firewall blocking access.

You can also specify a number of options on the command line. These are listed in the rdesktop manual page (run man rdesktop).
Download Rdesktop

___________________________
@hacking_Attack
@Hacking_Video
Dark Reading: Attacks/Breaches
New CrowdXDR Alliance Defines Data Exchange Standard for XDR

Google Cloud, Okta, ServiceNow, Zscaler, Netskope, Proofpoint, Extrahop, Mimecast, Claroty, and Corelight have joined the coalition.
Hacking Articles Tips Tricks Videos Tutorials
Photo
Kali Linux Tutorials
JSPanda : Client-Side Prototype Pollution Vulnerability Scanner

JSpanda is client-side prototype pollution vulnerability scanner. It has two key features, scanning vulnerability the supplied URLs and analyzing the JavaScript libraries’ source code.

However, JSpanda cannot detect advanced prototype pollution vulnerabilities.

How JSPanda works?

* Uses multiple payloads for prototype pollution vulnerability.
* Gathers all the links in the targets for scanning and add payloads to JSpanda-obtained URLs, navigates to each URL with headless Chromedriver.
* Scans all words in the source code of potentially vulnerable JavaScript library and it creates a simple JS PoC by finding the script gadget, helping you analyze the code manually.

Requirements

* Download latest version of Google Chrome and Chromedriver
* Selenium

Usage

Scan: python3.7 jspanda.py

* Add URLs to url.txt file, for instance : example.com

Basic Source Code Analysis : python3.7 analyze.py

* Add a JavaScript library’s source code to analyze.js
* Generate PoC code using analyze.py
* Execute PoC code on Chrome’s console. It pollutes all the words collected from the source code and show it on the screen. So it may generate false positive results. These outputs provide additional information to researchers, do not automate everything.

Source code analysis – Screenshot
https://1.bp.blogspot.com/-SZInObVpv48/YU17N8P7hSI/AAAAAAAAK8Y/xUFjEoj_Cp8JRCSUKHZ4Qv7geTFLYbBAQCLcBGAsYHQ/s1099/ss.png

Download

___________________________
@hacking_Attack
@Hacking_Video
Hacking Articles Tips Tricks Videos Tutorials
Photo
Kali Linux Tutorials
AutomatedLab : A Provisioning Solution And Framework That Lets You Deploy Complex Labs On HyperV And Azure With Simple PowerShell Scripts

AutomatedLab (AL) enables you to setup test and lab environments on Hyper-v or Azure with multiple products or just a single VM in a very short time. There are only two requirements you need to make sure: You need the DVD ISO images and a Hyper-V host or an Azure subscription. Requirements

Apart from the module itself your system needs to meet the following requirements:

* Windows Management Framework 5+ (Windows)
* .NET 4.7.1 (Windows PowerShell) or .NET Core 2.x (PowerShell 6+)
* Windows Server 2012 R2+/Windows 8.1+ (Hyper-V, Azure) or Linux (Azure)
* Recommended OS language is en-us
* Admin privileges are required
* ISO files for all operating systems and roles to be deployed
* Intel VT-x or AMD/V capable CPU
* A decent amount of RAM
* Low-Latency high-throughput storage (No spinning disks please, as there are issues related to them) Windows

* Windows Management Framework 5+
* Windows Server 2012 R2+/Windows 8.1+
* Recommended OS language is en-us
* Admin privileges are required Linux

* WSL supported, Azure Cloud Shell supported
* Tested on Fedora and Ubuntu, should run on any system capable of running PowerShell
* PowerShell 6+
* gss-ntlmssp to enable remoting (mandatory – no remoting, no way for AutomatedLab to do its thing)
* ip and route commands available
* Azure subscription – At the moment, AutomatedLab only works using Azure. KVM is planned for a later date. Download AutomatedLab

There are two options installing AutomatedLab:

* You can use the MSI installer published on GitHub.
* Or you install from the PowerShell Gallery using the cmdlet Install-Module. Please refer to the wiki for some details.

Installation

Raimund Andée [MSFT] edited this page on Feb 11, 2018 · 5 revisions

AutomatedLab (AL) is a bunch of PowerShell modules. For an easy installation, you can use the provided MSI or the PowerShell Gallery. MSI Installer

Download Link: https://github.com/AutomatedLab/AutomatedLab/releases

There are not many choices when installing AL.
https://1.bp.blogspot.com/-aGHvn5mG5HU/YV0i9pStKoI/AAAAAAAALBE/Z3dUC_D2ZEssgibZLTlY78d6PfrM5LYXACLcBGAsYHQ/s506/7.png
The options Typical and Complete are actually doing the same and install AL to the default locations. The PowerShell modules go to “C:\Program Files\WindowsPowerShell\Modules”, the rest to “C:\LabSources”.

As LabSources can grow quite big, you should go for a custom installation and put this component on a disk with enough free space to store the ISO files. This disk does not have to be an SSD. Do not change the location of the modules unless you really know what you are doing.
https://1.bp.blogspot.com/-2QaVc0TbGTc/YV0jcLgmlSI/AAAAAAAALBM/upu60CZEui8p2Tc8fGSOBTUYPcIL5GGBACLcBGAsYHQ/s506/8.png
Very important to AL is the LabSources folder that should look like this:
https://1.bp.blogspot.com/-2WbLjuMG0B0/YV0j5Xt-0DI/AAAAAAAALBU/R6jzWxsE39gycFgOyiAVrFthS-uZdUZggCLcBGAsYHQ/s728/9.png
If all that worked you are ready to go for Getting Started. PowerShell Gallery

AutomatedLab is provided on the PowerShell Gallery and updated on a regular basis. All the dependancies will be taken into account and some other modules are installed.

One important part of AutomatedLab is the LabSources folder that cannot be provided on the PowerShell Gallery. A new Cmdlet (New-LabSourcesFolder) has been introduced that downloads the AutomatedLab sources, extracts just the LabSources folder and puts it on the given drive.

There are only two commands that you need to run:

Install-Module -Name AutomatedLab -AllowClobber
New-LabSourcesFolder

Getting Started

Raimund Andée [MSFT] edited this page on Dec 23, 2017 · 16 revisions

After completed the Installation it is time to test instal[...]

___________________________
@hacking_Attack
@Hacking_Video