{"id":12142,"date":"2022-09-16T05:49:16","date_gmt":"2022-09-16T12:49:16","guid":{"rendered":"https:\/\/webdev.securin.xyz\/?post_type=patch_watch&p=12142"},"modified":"2023-02-17T13:30:24","modified_gmt":"2023-02-17T20:30:24","slug":"dhs-cisa-kevs-weekly-edition-18-patch-before-you-hit-the-deadline","status":"publish","type":"patch_watch","link":"https:\/\/webdev.securin.xyz\/patch_watch\/dhs-cisa-kevs-weekly-edition-18-patch-before-you-hit-the-deadline\/","title":{"rendered":"DHS CISA KEVs Weekly Edition 18: Patch Before You Hit the Deadline"},"content":{"rendered":"
The US Cybersecurity and Infrastructure Security Agency raises the alarm about known exploited vulnerabilities by adding new CVEs to the growing list of the KEV catalog. CISA added 22 new CVEs between September 08, 2022, and September 15, 2022.<\/strong><\/p>\n In this blog, we bring you all the DHS CISA KEVs that need to be prioritized for patching this week (September 12 to September 16, 2022).\u00a0<\/em><\/p>\n <\/p>\n CISA\u2019s KEVs is a collection of vulnerabilities that have been exploited by threat actors time and again. If left unpatched, these become low-hanging fruits that attackers can easily misuse.<\/p>\n A total of 11 known exploited vulnerabilities from the DHS CISA catalog should be fixed by federal agencies this week before September 12 to September 16, 2022.\u00a0 We urge all organizations to address these to safeguard their networks from attacks.<\/strong><\/p>\n We further analyzed these 11 KEVs and found that:<\/p>\n <\/p>\n <\/p>\n For 73% of vulnerabilities, exploit codes are readily available in the public domain. Attackers getting a hold of such exploits can easily breach networks and exploit exposures to penetrate deeper into the networks. Of these, 4 are of the highest class of exploits that allow for remote execution of custom code.<\/p>\n<\/li>\n The trending vulnerabilities are high on the radar of threat actors and attackers are constantly scouting the web for unpatched instances of such vulnerabilities.<\/p>\n<\/li>\n CVE-2022-26352, in particular, has associations with both ransomware and APT groups, making it highly dangerous. If exploited, organizations stand to lose their reputation, part with sensitive data, or even be locked out of their own systems.<\/p>\n<\/li>\n<\/ul>\n <\/p>\n Although all these CVEs are relatively new, they have 8 exploits so far, which make them dangerous.<\/p>\n <\/p>\n <\/p>\n This is a clear indication of how fast attackers are progressing today developing exploits for new vulnerabilities as they appear, sometimes even before organizations are made aware of the existence of such a flaw.<\/p>\n Our ransomware reports called out such vulnerabilities that were exploited as zero days, even before the vendor was aware of its presence. Read here to know more about our research<\/a>.<\/p>\n Apache is the worst affected with two critical vulnerabilities \u2013 an authentication bypass and an improper resource initialization vulnerability. There are 9 other vendors that have vulnerabilities in them.<\/p>\n <\/p>\n Organizations must keep themselves up to date with these vendor advisories and upgrade their products as and when new patches are released.<\/p>\n <\/p>\n Patching these vulnerabilities is of high priority, as they rank high and critical on the CVSS scoring scale. Exploiting such vulnerabilities will allow attackers to cause maximum damage to their victim networks.<\/p>\n <\/p>\n <\/p>\n <\/p>\n CVE-2022-26352 is associated with the HolyGhost ransomware group that is actively exploiting organizations across the globe. Organizations must give importance to this threat context and ensure the vulnerability is patched without delay.<\/p>\n <\/p>\n The following CWEs have caused the vulnerabilities that need to be patched this week. These are the weaknesses developers should be aware of and work to overcome while making their products.<\/p>\n <\/p>\n <\/p>\nWhy are these vulnerabilities important?<\/h2>\n
\n
How Far Back Do They Go?<\/h2>\n
<\/h2>\n
Which Vendors Are Affected?<\/h2>\n
Severity Scores<\/h2>\n
Software Weaknesses<\/h2>\n