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
The Problem With Patching: 7 Top Complaints
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
RyanSepe
RyanSepe,
User Rank: Ninja
4/25/2016 | 10:41:19 AM
Re: Suggested errata/addendums
Flash is definitely a pain point, especially for vulnerability management. I agree with you 100% to remove it. Especially at the server level where it is really not needed.
MKultra
MKultra,
User Rank: Apprentice
4/24/2016 | 3:32:40 PM
patching - the never ending story ...
hi fans,

well, i think the problem is the following:

when you install all patches and updates, you will get only new problems with vulnerabilities ...

then you need another patch to fix it - and so on !!!

its a never ending race between patch-programmers and blackhat-hackers - and the hackers have gone to win ...

sincerly

                 dipl.-ing.matthias klein (ANONYMOUS-member ans cybersecurity professional)

 

ps: when you have any trouble with malware, dont hesitate to ask me for free advice: pls call my mobile         +49-1575/7719806 or send me an email to m.klein1959(at)yahoo.com !!! i will help you ASAP ...
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
4/23/2016 | 9:26:36 AM
Suggested errata/addendums
I'd add a couple things to this very well thought out list:

* Don't just test your Windows updates.  Have and utilize a testbed for ALL your updates.  You never know when something might not play nice with something else.  (Remember the 3-day outage Verizon had on accounts receivable -- prevent customers from paying their bills -- because of an update gone awry?)

* The real solution for Flash is to JUST GET RID OF IT.  ;)
<<   <   Page 2 / 2


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
Creating an Effective Incident Response Plan
Security teams are realizing their organizations will experience a cyber incident at some point. An effective incident response plan that takes into account their specific requirements and has been tested is critical. This issue of Tech Insights also includes: -a look at the newly signed cyber-incident law, -how organizations can apply behavioral psychology to incident response, -and an overview of the Open Cybersecurity Schema Framework.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-4194
PUBLISHED: 2022-11-30
Use after free in Accessibility in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
CVE-2022-4195
PUBLISHED: 2022-11-30
Insufficient policy enforcement in Safe Browsing in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to bypass Safe Browsing warnings via a malicious file. (Chromium security severity: Medium)
CVE-2022-4175
PUBLISHED: 2022-11-30
Use after free in Camera Capture in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
CVE-2022-4176
PUBLISHED: 2022-11-30
Out of bounds write in Lacros Graphics in Google Chrome on Chrome OS and Lacros prior to 108.0.5359.71 allowed a remote attacker who convinced a user to engage in specific UI interactions to potentially exploit heap corruption via UI interactions. (Chromium security severity: High)
CVE-2022-4177
PUBLISHED: 2022-11-30
Use after free in Extensions in Google Chrome prior to 108.0.5359.71 allowed an attacker who convinced a user to install an extension to potentially exploit heap corruption via a crafted Chrome Extension and UI interaction. (Chromium security severity: High)