Awesome Red Teaming

I created list of Awesome Red Team / Red Teaming Resources.

https://github.com/yeyintminthuhtut/Awesome-Red-Teaming

This list is for anyone wishing to learn about Red Teaming but do not have a starting point.

Anyway, this is a living resources and will update regularly with latest Adversarial Tactics and Techniques.

You can help by sending Pull Requests to add more information.

[ CVE-2017-11749 ] FTP Commander 8.02 - Unsafe DLL Loading Vulnerability

1. OVERVIEW

The FTP Commander is vulnerable to Insecure DLL Hijacking
Vulnerability. Similar terms that describe this vulnerability
have been come up with Remote Binary Planting, and Insecure DLL
Loading/Injection/Hijacking/Preloading.

2. PRODUCT DESCRIPTION

FTP Commander is an FTP client for Windows. The program is developed by InternetSoft Corporation. Features include multiple connections, SSH, SSL, scheduler and backup tool, proxy and firewall support, chmod features, and localization for over 20 languages

3. VULNERABILITY DESCRIPTION

The FTP Commander application passes an insufficiently qualified path in
loading an external library when a user launch the application

Affected Library List
---------------------
# dwmapi.dll

4. VERSIONS AFFECTED

8.02 and prior

Tested Platform: Windows 7 x64 (Fresh Windows)

6. IMPACT

This occurs when an application fails to resolve a DLL because the DLL does not exist in the specified path or search directories. If this happens, a malicious Dll with the same name can be placed in the specified path directory leading to remote code execution.


7. SOLUTION

For application developers:
    Require set paths for DLLs in applications

For system administrators:
    Disable write permissions to relative application folders
    Utilize least privilege access to prevent users (and applications) from having too much access to the system

For both groups:
    Microsoft has a great article explaining the DLL-related registry keys and how they can be used to protect applications -
 http://blogs.technet.com/b/srd/archive/2010/08/23/more-information-about-dll-preloading-remote-attack-vector.aspx


8. VENDOR

 InternetSoft Corporation
www.internet-soft.com/ftpcomm.htm

9. CREDIT

This vulnerability was discovered by Ye Yint Min Thu htut, http://pentest.space

10. DISCLOSURE TIME-LINE

07-26-2017: vulnerability discovered
07-26-2017: notified vendor
08-29-2017: vulnerability disclosed

11. REFERENCES
https://support.microsoft.com/en-us/help/2389418/secure-loading-of-libraries-to-prevent-dll-preloading-attacks
https://cwe.mitre.org/data/definitions/427.html

[ CVE-2017-11748 ] Spider Player 2.5.3 - Unsafe DLL Loading Vulnerability

1. OVERVIEW

The Spider Media Player is vulnerable to Insecure DLL Hijacking Vulnerability. Similar terms that describe this vulnerability have been come up with Remote Binary Planting, and Insecure DLL Loading/Injection/Hijacking/Preloading.

2. PRODUCT DESCRIPTION

Spider Player is a skinnable audio player with full support for all major audio formats: MP3, AAC, WMA, OGG, FLAC and others. Its most interesting features include audio streaming, integration with Shoutcast and Icecast radio directories, lossless Internet radio recording, advanced CD Ripping and Converting capabilities, FreeDB integration, 32-sound processing for crystal-clear sound, customizable local and global hotkeys and crossfading support. Spider Player is small and blazingly fast, and uses very few system resources.

3. VULNERABILITY DESCRIPTION

The Spider Media player application passes an insufficiently qualified path in loading an external library when a user launch the application

Affected Library List

---------------------

# dwmapi.dll

# olepro32.dll

# dsound.dll

# AUDIOSES.dll

4. VERSIONS AFFECTED

 2.5.3 and prior

Tested Platform: Windows 7 x64 (Fresh Windows)


6. IMPACT

This occurs when an application fails to resolve a DLL because the DLL does not exist in the specified path or search directories. If this happens, a malicious Dll with the same name can be placed in the specified path directory leading to remote code execution.

7. SOLUTION

For application developers:
    Require set paths for DLLs in applications
For system administrators:
    Disable write permissions to relative application folders
    Utilize least privilege access to prevent users (and applications) from having too much access to the system
For both groups:
    Microsoft has a great article explaining the DLL-related registry keys and how they can be used to protect applications -

 http://blogs.technet.com/b/srd/archive/2010/08/23/more-information-about-dll-preloading-remote-attack-vector.aspx


8. VENDOR

VIT
https://spider-player.en.softonic.com/

9. CREDIT

This vulnerability was discovered by Ye Yint Min Thu htut, http://pentest.space

10. DISCLOSURE TIME-LINE

07-26-2017: vulnerability discovered
07-26-2017: notified vendor [ vendor's website was no long avaiable  ]
07-26-2017: reported to cert.org for coordination
08-29-2017: vulnerability disclosed

11. REFERENCES

https://support.microsoft.com/en-us/help/2389418/secure-loading-of-libraries-to-prevent-dll-preloading-attacks
https://cwe.mitre.org/data/definitions/427.html

PCMan FTP Server 2.0 Buffer Overflow [ Metasploit Modules ]

When i explored PCMan FTP exploit modules, only prompt for PUT and STOR command overflow modules. So I just porting for GET, NLST, ACCT, MKD, PORT command from each initial exploit.

Catch them below.

Github

pcman_acct.rb
pcman_get.rb
pcman_mkd.rb
pcman_nlst.rb
pcman_port.rb

PacketStorm

https://packetstormsecurity.com/files/142125/PCMAN-FTP-Server-2.0.7-MKD-Buffer-Overflow.html
https://packetstormsecurity.com/files/142124/PCMAN-FTP-Server-2.0.7-NLST-Buffer-Overflow.html
https://packetstormsecurity.com/files/142123/PCMAN-FTP-Server-2.0.7-GET-Buffer-Overflow.html
https://packetstormsecurity.com/files/142122/PCMAN-FTP-Server-2.0.7-ACCT-Buffer-Overflow.html

1337day

http://0day.today/exploit/27585
http://0day.today/exploit/27586
http://0day.today/exploit/27587
http://0day.today/exploit/27588



Cheers !

CRL Revocation Checker

I wrote this tiny CRL Revocation Checker where other scanners fail.

Clone it here https://github.com/yeyintminthuhtut/CRL-Revocation-Checker

Cheers !

Base CTF 2016 Pwn Challenges and Writeup ( Part V )

Pwn06: Try Harder!

Challenges Download:

Solution:

let begin with debugger.

Damn, he wanted “BABE” ! ;)

So, let find the crash point and combine into final payload.

  Done ! :)

Enjoy guys !

Base CTF 2016 Pwn Challenges and Writeup ( Part IV )

Pwn05: Talk another one !

Challenges Download:

Solution:

It is simple buffer overflow challenge. You have to find crash point and function address to print flag.

Let create pattern to find crash point as smart way.

Save as pwn.

Run with the debugger and load the payload to get offset.

 Then, let explore the suspected function.

 Got it at 0x0804846b !

 Let create final payload to get flag.

 Pwned ! :)

Enjoy guys !

Base CTF 2016 Pwn Challenges and Writeup ( Part III )

Pwn04: Bypass me !

Challenges Download:

Solution:

For this challenge, you have to bypass ARP filtering to get grant.

Let seek for authorized MAC address.

Found 00:0C:29:04:a1:a , you can fuzz [0 to F] to get last char and replace with your existing MAC address.  

Easy ? :)

Cheers !

Ye Yint Min Thu Htut

Base CTF 2016 Pwn Challenges and Writeup ( Part II )

Challenges Download:

“System is calling date” is hint for that challenge. It is also principle privilege escalation challenge.

Let create our own “Date” to get grant.

Pwned ! 

Base CTF 2016 Pwn Challenges and Writeup ( Part I )

For Base CTF 2016 (Myanmar Cyber Security Competition), I facilitated in making some challenges.

Our challenges are primarily aimed for entry level participants of CTF to polish their CTF knowledge. We will deliver more hardcore challenges in coming CTFs once you ready :).

Congrats to all solvers of our challenges.

Ok, let start the writeup for your ref.

Pwn02: Find me!

Challenges Download

Solution:

Yea, it was inspecting your UID for grant.

You needed to find correct UID or bypass it. We will use bypass method.

Run it in debugger.

Damn, checkpoint is there.

Let set a breakpoint, and change EAX value to become UID 1256 ( 0x4e8 ).

 Granted ! :)

Enjoy guys !