Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
How Retro Malware Feeds the New Threat Wave
Newest First  |  Oldest First  |  Threaded View
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
10/13/2014 | 4:41:37 PM
Re: What's old is new
So true, Anthony. Everyone is looking for the best ROI -- good guys and bad guys alike. 
adibello
50%
50%
adibello,
User Rank: Author
10/13/2014 | 4:31:52 PM
Re: What's old is new
As you suggest @Sara, it's always more cost effective to reuse proven code where possible than to create new code from scratch, using new vulnerabilities or obfuscation techniques to successfully inject such code into the enterprise to your point @Marilyn. The folks creating and selling malware are just as organized and budget conscious as their white hat counterparts, looking to leverage methods which offer the greatest return on investment wherever they can.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
10/7/2014 | 7:54:32 AM
Re: What's old is new
I like your fashion analogy, @Sara. I'm the last person to comment on fashion trends, but to take it the analogy one step further, whenever a retro style comes back into vogue, there seems to always be some new twist that makes your old garb not quite the right look or feel. So it seems with retro malware. It's familiar but yet new enough that existing antimalware and practices won't be effective...
Sara Peters
50%
50%
Sara Peters,
User Rank: Author
10/6/2014 | 4:34:09 PM
What's old is new
Well cybercrime is rather fashionable these days; why shouldn't it follow the same rules that the fashion/beauty industry does? Do you think that attackers simply wait until we let our guard down, to start using the old stuff we've stopped looking for? The whole "just when you thought it was safe to go back in the water," approach? I'm not entirely certain, though, why that's preferable. I suppose it's cheaper. You don't have to go invest in brand new malware toolkits and such. 


Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.