Microsoft Patch Tuesday, March 2022 Edition

Microsoft on Tuesday released software updates to plug at least 70 security holes in its Windows operating systems and related software. For the second month running, there are no scary zero-day threats looming for Windows users (that we know of), and relatively few “critical” fixes. And yet we know from experience that attackers are already trying to work out how to turn these patches into a roadmap for exploiting the flaws they fix. Here’s a look at the security weaknesses Microsoft says are most likely to be targeted first.

Greg Wiseman, product manager at Rapid7, notes that three vulnerabilities fixed this month have been previously disclosed, potentially giving attackers a head start in working out how to exploit them. Those include remote code execution bugs CVE-2022-24512, affecting .NET and Visual Studio, and CVE-2022-21990, affecting Remote Desktop Client. CVE-2022-24459 is a vulnerability in the Windows Fax and Scan service. All three publicly disclosed vulnerabilities are rated “Important” by Microsoft.

Just three of the fixes this month earned Microsoft’s most-dire “Critical” rating, which Redmond assigns to bugs that can be exploited to remotely compromise a Windows PC with little to no help from users. Two of those critical flaws involve Windows video codecs. Perhaps the most concerning critical bug quashed this month is CVE-2022-23277, a  remote code execution flaw affecting Microsoft Exchange Server.

“Thankfully, this is a post-authentication vulnerability, meaning attackers need credentials to exploit it,” Wiseman said. “Although passwords can be obtained via phishing and other means, this one shouldn’t be as rampantly exploited as the deluge of Exchange vulnerabilities we saw throughout 2021. Exchange administrators should still patch as soon as reasonably possible.”

CVE-2022-24508 is a remote code execution bug affecting Windows SMBv3, the technology that handles file sharing in Windows environments.

“This has potential for widespread exploitation, assuming an attacker can put together a suitable exploit,” Wiseman said. “Luckily, like this month’s Exchange vulnerabilities, this, too, requires authentication.”

Kevin Breen, director of cyber threat research at Immersive Labs, called attention to a trio of bugs fixed this month in the Windows Remote Desktop Protocol (RDP), which is a favorite target of ransomware groups.

CVE-2022-23285, CVE-2022-21990 and CVE-2022-24503 are a potential concern especially as this infection vector is commonly used by ransomware actors,” Breen said. “While exploitation is not trivial, requiring an attacker to set up bespoke infrastructure, it still presents enough of a risk to be a priority.”

March’s Patch Tuesday also brings an unusual update (CVE-2022-21967) that might just be the first security patch involving Microsoft’s Xbox device.

“This appears to be the first security patch impacting Xbox specifically,” said Dustin Childs from Trend Micro’s Zero Day Initiative. “There was an advisory for an inadvertently disclosed Xbox Live certificate back in 2015, but this seems to be the first security-specific update for the device itself.”

Also on Tuesday, Adobe released updates addressing six vulnerabilities in Adobe Photoshop, Illustrator and After Effects.

For a complete rundown of all patches released by Microsoft today and indexed by severity and other metrics, check out the always-useful Patch Tuesday roundup from the SANS Internet Storm Center. And it’s not a bad idea to hold off updating for a few days until Microsoft works out any kinks in the updates: AskWoody.com usually has the lowdown on any patches that may be causing problems for Windows users.

As always, please consider backing up your system or at least your important documents and data before applying system updates. And if you run into any problems with these patches, please drop a note about it here in the comments.

from Krebs on Security https://ift.tt/QVmYO2o
via IFTTT

Las bibliotecas de código abierto más importantes

bibliotecas

Siempre se piensa que los proyectos más importantes en cuanto al código abierto son los programas, el software. Pero siempre se nos olvida algo más vital incluso, y que sin ello no serían posible todos esos otros proyectos (Linux, Apache, LibreOffice, WINE, Firefox, KDE Plasma, etc.). Me refiero a las bibliotecas de las que depende todo ese software, de hecho, son piezas críticas, ya que si faltan o si tienen cualquier problema, pueden devastar multitud de proyectos (véanse casos como el sabotaje a una de estas bibliotecas o el impacto de la vulnerabilidad en log4j).

Por este motivo, el LISH o Laboratorio para la Ciencia de la Innovación de Hardvard, en colaboración con la OpenSSF de la Linux Foundation, han realizado un estudio exhaustivo de la importancia de las bibliotecas de código abierto. Unas bibliotecas que se emplean para multitud de proyectos de código abierto y software libre, además de estar presentes en sistemas de producción de miles de empresas en todo el mundo.

En el estudio se tomó una amplia muestra de multitud de empresas que dieron datos. Y no solo con el objetivo de conocer las bibliotecas más populares, sino también ayudar a blindar esos proyectos por su importancia., tanto desde el punto de vista de la dependencia que se tiene de ellas como desde el punto de vista de la seguridad, ya que cualquier vulnerabilidad en alguna de ellas afectaría a miles de sistemas (bancos, escuelas, empresas, gobiernos, hospitales, industria, vehículos, hogares,…).

Además, en este estudio la Universidad de Harvard ha destacado la necesidad de:

  • Tener nombres estandarizados.
  • Simplificar la complejidad para el control de versiones.
  • Gran parte de los proyectos de bibliotecas FOSS a veces dependen de unas cuantas personas o de una sola persona. Y, en muchas ocasiones, sin recursos.
  • Mejorar la seguridad.
  • Limpiar el software heredado en el espacio de código abierto. Ejecutar proyectos demasiado toscos y antiguos supone un riesgo.

Más información – Ver PDF del informe 1

Más información – Ver PDF del informe 2

from Linux Adictos https://ift.tt/B4S2mYE
via IFTTT