[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAAHK0WTjVf=_-fAgiR4DDg5A8uTBs8N7VSo4R4tU=1YX8i7nUA@mail.gmail.com>
Date: Tue, 3 May 2022 10:01:22 -0400
From: malvuln <malvuln13@...il.com>
To: fulldisclosure@...lists.org
Subject: [FD] RedLine.Stealer / Code Execution
Discovery / credits: Malvuln - malvuln.com (c) 2022
Original source:
https://malvuln.com/advisory/0adb0e2ac8aa969fb088ee95c4a91536.txt
Contact: malvuln13@...il.com
Media: twitter.com/malvuln
Threat: RedLine.Stealer
Vulnerability: Code Execution
Description: RedLine looks for and loads a DLL named "wow64log.dll" in
Windows\System32. Therefore, we can drop our own DLL to intercept and
terminate the malware. The exploit dll will simply display a Win32API
message box and call exit(). Our RedLine exploit DLL must export
"InterlockedExchange" function or it fails with error. We do not need to
rely on hash signature or third-party product, the malware vuln will do the
work for us. Endpoint protection systems and or antivirus can potentially
be killed prior to executing malware, but this method cannot as theres
nothing to kill the DLL just lives on disk waiting. From defensive
perspective you can add the DLLs to a specific network share containing
important data as a layered approach. All basic tests were conducted
successfully in a virtual machine environment.
Family: RedLine
Type: PE32
MD5: 0adb0e2ac8aa969fb088ee95c4a91536
Vuln ID: MVID-2022-0578
Exploit/PoC:
Video PoC URL: https://www.youtube.com/watch?v=HQ2JTyckZpo
Exploit/PoC:
1) Compile the following C code as "wow64log.dll" as x64
2) Copy the DLL to Windows/System32
3) Run the malware and BOOM!
#include "windows.h"
#include "stdio.h"
//By malvuln - 5/2022
//Target: RedLine Stealer
//MD5: 0adb0e2ac8aa969fb088ee95c4a91536
/** DISCLAIMER:
Author is NOT responsible for any damages whatsoever by using this software
or improper malware
handling. By using this code you assume and accept all risk implied or
otherwise.
**/
//compile as x64
//gcc -c wow64log.c
//gcc -shared -o wow64log.dll wow64log.o
//DLL must live under Windows/System32 dir
BOOL APIENTRY DllMain(HINSTANCE hInst, DWORD reason, LPVOID reserved){
switch (reason) {
case DLL_PROCESS_ATTACH:
MessageBox(NULL, "Code Exec", "by malvuln", MB_OK);
exit(0);
break;
}
return TRUE;
}
extern __declspec(dllexport) WINBASEAPI LONG WINAPI InterlockedExchange
(LONG volatile *Target, LONG Value){
exit(1);
}
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).
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Powered by blists - more mailing lists