Malware News
16.2K subscribers
1.64K photos
7 videos
130 files
8.3K links
The latest NEWS about malwares, DFIR, hacking, security issues, thoughts and ...

Partner channel: @cveNotify

For ads: https://telega.io/c/malwr
Download Telegram
[DrayTek - Unauthenticated RCE in Draytek Vigor 2960, 3900 and 300B (CVE-2020-8515)](https://www.skullarmy.net/2020/01/draytek-unauthenticated-rce-in-draytek.html)
πŸ—£cyberg0100


πŸŽ–@malwr
#Splunk Boss of the SOC v3 Dataset Released!
https://www.splunk.com/en_us/blog/security/botsv3-dataset-released.html

BOTS 3.0 includes a Tools and Training scenario to help less experienced folks gain a foothold and to help everyone get familiar with the environment. The dataset also includes a cloud scenario that illustrates security issues that organizations commonly encounter when moving workloads to Amazon AWS and Microsoft Azure.


πŸŽ–@malwr
Reading content of RAM
I was looking at the way to read what kind of data is stored in my ram. But can't find a definitive answer. Can anyone help me out?
πŸ—£sahil098

Reading the data isn't so hard. You'd need a tool which can image and dump the data...ftk imager can do it for you and is free. There are loads of others.

Deciphering it on the other hand is more difficult. You might want to read up on volatility, or you could try running a scan across the memory image for file types of interest.
πŸ‘€Briggykins


πŸŽ–@malwr
Cyber FastTrack Spring 2020 CTF Writeups
πŸ—£tsuto

Thank you so much! I made top 100 but with only about 50% complete and there were some that were on the "tip of my tongue" for hours but I couldn't secure the flag. First individual CTF for me so it was a learning experience but overall I had a blast.

This has been really helpful for me to learn from! Congrats on 1st and thanks a ton!
πŸ‘€SentientOwl_


πŸŽ–@malwr
Cisco Password Cracking and Decrypting Guide
πŸ—£InfosecMatter

For type 7 passwords, you can create a key chain with a key-string 7, then do a show key-chain and it will output the type 7 password in cleartext
πŸ‘€clearmoon247


πŸŽ–@malwr
X86 Inline Assembly
Hello!
I'm new to inline assembly, whilst I do have experience with assembly, it is mostly geared towards programming micro controllers. I'm trying to get an assignment done, and I have been researching inline assembly. My goal is to successfully implement the functionality of what getchar and putchar would do using inline assembly.(Reading a character from stdin, and putting a character on stdout).
I don't know if this means anything but I'm running this on a Linux machine, compiling with gcc.
Apparently it uses AT&T style as opposed to Intel style, This must use x86 inline assembly.


I'm trying to get the steps down.
Write to std_out

It seems I have to load, register %%eax with 4 (the call for sys\_write).
Load %%ebx with the file descriptor, in this case 1.
Load %%edx with the size, in this case 1.
Load %%ecx with a const char *, a pointer to the character.

My first implementation is here:

int main()
{
char p = 'p';
int ret;
__asm__ __volatile__(
"syscall"
:"=a"(ret)
:"a"(4), "b"(1), "c"(&p), "d"(1)
: "memory"
);
return 0;
}

This code above doesn't output anything, but ret is equivalent to -14/

A second implementation, without using extended Assembly
int main()
{
char c = 'c';
char * pointer = &c;
__asm__ __volatile__(
"mov $1, %%ebx\t\n"
"mov $1, %%edx\t\n"
"mov %1, %%ecx\t\n"
"mov $4, %%eax\t\n"
"syscall"
:
:"r"(pointer)
:
);
// printf("foo+bar=%d\n", foo);
return 0;
}

This code doesn't compile, I get a invalid 'asm': operand number out of range.


I'm trying to work through this before attempting writing putchar, as I may have foundational errors.

I'd appreciate any possible aid/hints!


Thanks in advance!
πŸ—£StandardSBUStudent

Are you compiling for 32-bit or 64-bit? They have different system call numbers and calling conventions.

For 32-bit: Pass parameters in eax/ebx/ecx/edx (i.e. syscall number in eax) and use int $0x80 to execute. sys_write is 4.

For 64-bit: Pass parameters in rax/rdi/rsi/rdx and use syscall. sys_write is 1.

For your second example note that the first operand is %0. See here
πŸ‘€0xa0000


πŸŽ–@malwr