It may add a slight overhead to the interactive sleep throughput ProxyPass processing logic is far from perfect and is really buggy (and oh boy its ugly!). Weird forms of configuration files can derail RedWarden parser and make it complain. Easiest approach to overcome this would be to copy example-config.yaml and work on it instead.
Oh my god why is this code such an engineerical piece of crap?
The code is ONE FUCKING BIG HELL OF A MESS - I admit that - and there's an honest reason for that too: the project was being developed 90% during the actual Red Team engagements. As we all know, these sorts of engagements entail so many things to do, leaving close to no time for a proper complex tool development. Not to mention criticality of this program in project's setup. The tool initialy started as a simple proxy script written in Python2, to then evolve as a proxy with plugins, received malleable_redirector plugin - and since then I've been trying really hard to keep proxy2 maintain backwards compatibility (poor me, I was like Microsoft!) with other plugins I've made for it and stick to its original purpose. Time has come though to let it go, rebrand it and start fixing all the bad code smells introduced. With all that said, please do express some level of compassion for me when raising issues, submitting pull requests and try to help rather than judge! :-) Thanks!
TODO
Research possibility to use Threat Intelligence (https://www.kitploit.com/search/label/Threat%20Intelligence) feeds to nefarious purposes - like for instance detecting Security Vendors based on IPs Add support for MaxMind GeoIP database/API Implement support for JA3 signatures in both detection & blocking and impersonation to fake nginx/Apache2/custom setups. Add some unique beacons tracking logic to offer flexilibity of refusing staging and communication processes at the proxy's own discretion Introduce day of time constraint when offering redirection capabilities (proxy only during office hours) Add Proxy authentication and authorization (https://www.kitploit.com/search/label/Authorization) logic on CONNECT/relay. Add Mobile users targeted redirection Add configuration options to define custom HTTP headers to be injected, or ones to be removed Add configuration options to require specific HTTP headers to be present in requests passing ProxyPass criteria. Interactive interface allowing to type simple characters controlling output logging verbosity, similarly to Nmap's Rewrite Malleable profile parser logic to pyMalleableC2 (https://github.com/Porchetta-Industries/pyMalleableC2). When I first started coding my own parser logic, there was no such toolkit on Github. Refactor all the codebase
Author
">Mariusz B. / mgeeky, '19-'21



Download RedWarden (https://github.com/mgeeky/RedWarden)

___________________________
@hacking_Attack
@Hacking_Video

Solution and explanation of tips for Intigriti’s 0521 XSS challenge — by @GrumpinouT

This month’s (May 2021) XSS challenge by Intigriti was created by me (with some additions by Inti). In this article, I will explain my…Continue reading on InfoSec Write-ups »
Read more...

Install kxss on Kali Linux

kxss : to identify XSS vulnerable parameters.Continue reading on Medium »
Read more...

My First Bounty on a Simple Bug

Hello Folks 👋 , in this write-up I will tell you how I ended up getting a 150$ bounty on a Bugcrowd Program.Continue reading on Medium »
Read more...

My First Bounty on a Simple Bug
https://sapt.medium.com/my-first-bounty-on-a-simple-bug-212e8c4ea077?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

Hello Folks 👋 , in this write-up I will tell you how I ended up getting a 150$ bounty on a Bugcrowd Program.Continue reading on Medium » (https://sapt.medium.com/my-first-bounty-on-a-simple-bug-212e8c4ea077?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

Install kxss on Kali Linux
https://medium.com/@sherlock297/install-kxss-on-kali-linux-e0edd5d169af?source=rss------bug_bounty-5

kxss : to identify XSS vulnerable parameters.Continue reading on Medium » (https://medium.com/@sherlock297/install-kxss-on-kali-linux-e0edd5d169af?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

Exploit Collector
Backdoor.Win32.Neakse.bit Insecure Permissions

https://4.bp.blogspot.com/-gQsa2Au6OFw/WWlvKe9cGFI/AAAAAAAAIME/7MuhuX3Jqy0CeEu0oyVXmXST8BDpKvIGgCLcBGAs/s1600/h15.png
Backdoor.Win32.Neakse.bit malware suffers from an insecure permissions vulnerability.

MD5 | 9ead3ac44ed6c17d914d36b4ab7b6698

Download
Discovery / credits: Malvuln - malvuln.com (c) 2021
Original source: https://malvuln.com/advisory/20863ba09c31037b1b3220fc6da100e1.txt
Contact: malvuln13@gmail.com
Media: twitter.com/malvuln

Threat: Backdoor.Win32.Neakse.bit
Vulnerability: Insecure Permissions
Description: The malware creates two insecure dirs housing DLLs under c:\ drive and grants change (C) permissions to the authenticated user group. Standard users can rename the executables dropped by the malware to disable it or replace it with their own executable. Then wait for a privileged user to logon to the infected machine to potentially escalate privileges.
Type: PE32
MD5: 20863ba09c31037b1b3220fc6da100e1
Vuln ID: MVID-2021-0238
Disclosure: 06/06/2021

Exploit/PoC:
C:\>cacls codecs
C:\codecs BUILTIN\Administrators:(OI)(CI)(ID)F
NT AUTHORITY\SYSTEM:(OI)(CI)(ID)F
BUILTIN\Users:(OI)(CI)(ID)R
NT AUTHORITY\Authenticated Users:(ID)C
NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(ID)C
C:\>dir codecs
Volume in drive C has no label.

Directory of C:\codecs

04/06/2004 12:04 AM 548,919 colorcvt.dll
04/06/2004 12:05 AM 65,602 cook.dll
04/06/2004 12:07 AM 266,306 erv3.dll
04/06/2004 12:08 AM 479,298 erv4.dll
04/06/2004 12:05 AM 155,702 ralf.dll
04/06/2004 12:05 AM 102,465 sipr.dll
6 File(s) 1,618,292 bytes

C:\>cacls common
C:\common BUILTIN\Administrators:(OI)(CI)(ID)F
NT AUTHORITY\SYSTEM:(OI)(CI)(ID)F
BUILTIN\Users:(OI)(CI)(ID)R
NT AUTHORITY\Authenticated Users:(ID)C
NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(ID)C
C:\>dir common
Volume in drive C has no label.

Directory of C:\common

12/06/2002 02:02 PM 395,776 encn3260.dll
04/06/2004 12:08 AM 368,732 rembrdcst.dll
2 File(s) 764,508 bytes
Disclaimer: The information contained within this advisory is supplied "as-is" with no warranties or guarantees of fitness of use or otherwise. Permission is hereby granted for the redistribution of this advisory, provided that it is not altered except by reformatting it, and that due credit is given. Permission is explicitly given for insertion in vulnerability databases and similar, provided that due credit is given to the author. The author is not responsible for any misuse of the information contained herein and accepts no responsibility for any damage caused by the use or misuse of this information. The author prohibits any malicious use of security related information or exploits by the author or elsewhere. Do not attempt to download Malware samples. The author of this website takes no responsibility for any kind of damages occurring from improper Malware handling or the downloading of ANY Malware mentioned on this website or elsewhere. All content Copyright (c) Malvuln.com (TM).

Source:packetstormsecurity.com

___________________________
@hacking_Attack
@Hacking_Video

Exploit Collector
WordPress Smart Slider-3 3.5.0.8 Cross Site Scripting

https://4.bp.blogspot.com/-I-n26yI3Cmk/WWlvWxoCyUI/AAAAAAAAIOM/Fl6K91g5v_sGMssa7qzCkbxeapM4aUyUACLcBGAs/s1600/h50.png
WordPress Smart Slider-3 plugin version 3.5.0.8 suffers from a persistent cross site scripting vulnerability.

MD5 | 3f02ab5c7a9e2da15d2909b4f43ff52b

Download
# Exploit Title: WordPress Plugin Smart Slider-3 3.5.0.8 - 'name' Stored Cross-Site Scripting (XSS)
# Exploit Author: Hardik Solanki
# Date: 05/06/2021
# Software Link: https://wordpress.org/plugins/smart-slider-3/
# Version: 3.5.0.8
# Tested on Windows

*How to reproduce vulnerability:*

1. Install WordPress 5.7.2
2. Install and activate the "*Smart Slider 3" Version 3.5.0.8* plugin
3. Navigate to "*Dashboard* and create a "*New Project*".
4. Enter the JavaScript payload "**" into the "*Name*" field.
5. You will observe that the Project has been created with malicious
JavaScript payload "" and hence
project has been* created/stored* and thus JavaScript payload is executing
successfully.

*XSS IMPACT:*
1: Steal the cookie
2: User redirection to a malicious website

Source:packetstormsecurity.com

___________________________
@hacking_Attack
@Hacking_Video

Exploit Collector
OptiLink ONT1GEW GPON 2.1.11_X101 Remote Code Execution

___________________________
@hacking_Attack
@Hacking_Video