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
It Takes an Average 38 Days to Patch a Vulnerability
Newest First  |  Oldest First  |  Threaded View
tdsan
tdsan,
User Rank: Ninja
8/24/2018 | 5:17:33 PM
I enjoyed reading the post
Interesting comment from one of the researchers, "Last year, only one in 1,200 attempts were successful, making it tough to separate breaches from attack attempts.". So last year, the money count was 9.7 Billion dollars, so 9,700,000,000/1200 = 8,083,333.33. So that means on average, they came out with 8M. I am not sure about you, but that is pretty extensive for someone not working or investing in the stock market.

"The second most common was SQL injection, which was leveraged to access sensitive data or run OS commands to gain further access into a target system. " - Maybe I missed something, I thought the first rule of thumb would be to install the database on a separate system other than the DB/Application sitting together, I think from that standpoint, isn't the person asking for trouble, just a rule of thumb.

"those are injection flaws, broken authentication, sensitive data exposure, XML external entities, and broken access control." - And isn't this just plain human error and no oversight on the part of the manager or director.

RASP - Run-Time Application Self Protection. This is interesting, they are developing this for the various phones but I don't see the development for servers or desktops. I do think machine learning is taking over in this space where the algorithms and teaching sequences are getting more complicated and the systems are learning. There was an incident where Facebook allowed two machines to learn from each other, they allowed the machine to communicate with each other and the systems started communicating with each other in a totally different language, the researchers were so frightened of the incident that they stopped the research project all together - https://goo.gl/2VcyRw. The last time I looked at Transformers, this occurred as well. All I can say is wow, we should have allowed them to communicate in a controlled environment to see what they would have come up with, they probably would have gone out of the electrical circuits to learn all the human behavior flaws, that would have been interesting.

"If you have an app on the Internet, it'll get attacked eventually," he says – and to use the right tools and data to minimize them." - I especially agree with this point, but at the end of the day, isn't security a facade, at the end of the day if we look into the imperceivable deep areas of the mind, where if put in the right circumstances, we would all break down and do the things that we said we would not (whether it would be money, fame, prestige or family concerns). I hope I never run down that path but who knows, only the future holds that truth.

Please keep the wonderful articles coming.

Todd

 


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
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-22497
PUBLISHED: 2022-05-24
IBM Aspera Faspex 4.4.1 and 5.0.0 could allow unauthorized access due to an incorrectly computed security token. IBM X-Force ID: 226951.
CVE-2022-29334
PUBLISHED: 2022-05-24
An issue in H v1.0 allows attackers to bypass authentication via a session replay attack.
CVE-2022-29337
PUBLISHED: 2022-05-24
C-DATA FD702XW-X-R430 v2.1.13_X001 was discovered to contain a command injection vulnerability via the va_cmd parameter in formlanipv6. This vulnerability allows attackers to execute arbitrary commands via a crafted HTTP request.
CVE-2022-29333
PUBLISHED: 2022-05-24
A vulnerability in CyberLink Power Director v14 allows attackers to escalate privileges via a crafted .exe file.
CVE-2021-3597
PUBLISHED: 2022-05-24
A flaw was found in undertow. The HTTP2SourceChannel fails to write the final frame under some circumstances, resulting in a denial of service. The highest threat from this vulnerability is availability. This flaw affects Undertow versions prior to 2.0.35.SP1, prior to 2.2.6.SP1, prior to 2.2.7.SP1,...