lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <w73S-GpO3kZOFCVeRJbXjMJkKkIgPmRBgb2e8EAagZKi-DgQV2c1djs44ydeTDXmMHd8VrbVA_Z-3_BH-aDdtfQ57bGjFj1lIsXzCED5WJ8=@protonmail.ch>
Date: Wed, 13 Jan 2021 07:42:17 +0000
From: "network.mp4 via Fulldisclosure" <fulldisclosure@...lists.org>
To: "fulldisclosure@...lists.org" <fulldisclosure@...lists.org>
Subject: Re: [FD] Backdoor.Win32.NinjaSpy.c / Remote Stack Buffer Overflow

Matthew Fernandez <matthew.fernandez@...il.com> at Fri, 8 Jan 2021 07:53:44 -0800:
> How should we be treating the stream of malware vulnerabilities you’ve reported recently? If something is malware, surely I want to remove it from my machine anyway? I’m all for full disclosure, but I’m just trying to understand if there’s anything actionable list members could do with this information. Thank you for your work on this, which is quite interesting to follow by the way.
I personally think that those malware vulnerabilities are a great way to detect malware, however, they may be used a lot to infect vulnerable computers with even more malware. But it's still a backdoor and those are great for education about how such backdoors can be prevented, as list subscribers can see what mistakes did the programmer do and what mistakes they should not make.

Regards!

_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: http://seclists.org/fulldisclosure/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ