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
6 Most Dangerous New Attack Techniques in 2015
Newest First  |  Oldest First  |  Threaded View
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
4/23/2015 | 3:24:13 PM
Data Engineering
Of these, I think it is Technique #1 that interests me the most in terms of how lethal it can actually be.  When you look at Data Engineering (acquire->ingest->transform->store->retrieve) programmatically, there is this incredible opportunity to inject AI into the software that drives illegal data engineering, especially when the source is internal, such as a whistleblower or disgruntled worker, and someone who can help place malicious code onsite.  Then, with endpoints working together, cyber criminals can program data manipulation activities that are innocuous and ride everyday traffic, raise no alarms, and have as their key attribute patience.  Sensitive data leaks have the potential to become almost imperceptible with the addition of dummy endpoints (shadow companies, banks, etc) receiving information from both malicious sources and unsuspecting (depending on how well the insider is able to plant malicious code).  In short, data science holds the key to taking what used to be blatant and forensic-heavy incidents and now burying it into the white noise of everyday electronic traffic. 
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/23/2015 | 9:34:53 AM
IoT
I definitely agree with most of these, especially with the IoT. Devices are being made smart down to the nearest toaster. (Aside from the satire in that statement the big example I have in mind right now is the smart watch) These devices will only become more prevalent and for security to keep up will be a challenge.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-35397
PUBLISHED: 2021-08-04
A path traversal vulnerability in the static router for Drogon from 1.0.0-beta14 to 1.6.0 could allow an unauthenticated, remote attacker to arbitrarily read files. The vulnerability is due to lack of proper input validation for requested path. An attacker could exploit this vulnerability by sending...
CVE-2021-36483
PUBLISHED: 2021-08-04
DevExpress.XtraReports.UI through v21.1 allows attackers to execute arbitrary code via insecure deserialization.
CVE-2021-37231
PUBLISHED: 2021-08-04
A stack-buffer-overflow occurs in Atomicparsley 20210124.204813.840499f through APar_readX() in src/util.cpp while parsing a crafted mp4 file because of the missing boundary check.
CVE-2021-37232
PUBLISHED: 2021-08-04
A stack overflow vulnerability occurs in Atomicparsley 20210124.204813.840499f through APar_read64() in src/util.cpp due to the lack of buffer size of uint32_buffer while reading more bytes in APar_read64.
CVE-2021-32813
PUBLISHED: 2021-08-03
Traefik is an HTTP reverse proxy and load balancer. Prior to version 2.4.13, there exists a potential header vulnerability in Traefik's handling of the Connection header. Active exploitation of this issue is unlikely, as it requires that a removed header would lead to a privilege escalation, however...