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
Predicting Vulnerability Weaponization
Newest First  |  Oldest First  |  Threaded View
tdsan
tdsan,
User Rank: Ninja
6/29/2019 | 3:22:22 PM
Logical review of the analytics process
With a data set established, we need analytical models to gain predictive insights. By looking at historical weaponization trends, we can train algorithms to look across diverse types of data and identify the combination of traits that best predicts which vulnerabilities will be weaponized by attackers in the wild. Just as importantly, this approach can predict the speed at which a given vulnerability is likely to be weaponized.
  •  Traits and vulnerabilities - Couldn't we start with the threats that actually succeeded. Then take that information and categorize it using the risk score from CVE or others. take that information and create a relationship database (i.e SharedDB or No-SQL columnar DB) where big data comes into play to establish or identify those relationships, this will help the end-user determine the number of similarities between the variants or possible vulnerabilities that exist
  • Locations - identify where the code is coming from by associating the geographic regions, with the code, actors and success levels, this allows for those models (again Big Data) to start narrowing down the attacks to specific regions based on the type of attack, its function, success rate and locale (determine the type of attack and method of attack based on their success rate and design).
  • Finally, use ML to look at the attack vectors from a historical standpoint, the results from BigData can now inject its findings into the ML DB and from those relationshps, we can determine based on risk score if something else will occur as part of the variants evolution (most systems build on itself).

ML Concepts

 

Big Data
alpana.b
alpana.b,
User Rank: Apprentice
6/20/2019 | 6:42:52 AM
Automated Testing
Can there be a solution as Automated Testing? Or a testing that can run 24/7  and immediately identify existing or newly created vulnerabilities? At least for DDoS testing, I know there is such product available - this product doesn't need any maintenance window, for enterprises its a business as usual and testing report is handed over to security team to tackle issues with vendor. https://mazebolt.com/ddos-radar 

Do you see any such product for other security areas which can emerge as new technology?
dmddd
dmddd,
User Rank: Apprentice
6/13/2019 | 11:32:09 PM
Reference
Death Srinivas, Thanks for the interesting article. Would you mind sharing the reference of the underlying research paper? Best regards, David


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
Everything You Need to Know About DNS Attacks
It's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask. Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted. Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-33196
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
CVE-2023-33185
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
CVE-2023-33187
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `ty...
CVE-2023-33194
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn’t fix it when clicking save. This issue was...
CVE-2023-2879
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file