Tech

Samba unveils a monstrous flaw that endangers your local network

Samba, the data transfer protocol between Windows and Unix operating systems is the victim of a huge security breach. This allows hackers to execute malicious code remotely. To fix it, just install the latest version of the software.

Credits: Pexels

You may be using it without even knowing it, and yet it isone of the most important Windows protocols. Samba allows the transfer of data between Windows and Unix devices (including macOS and Linux), in particular in order to share printers and files within a local network. Especially useful in business, it can also intervene at home for users using a NAS. Therefore you would do well to check that your version is up to date.

Indeed, the Samba Team recently announced that its software contains a massive security breach. Dubbed CVE-2021-44142, this is an out-of-bounds read issue present in the vfs_fruit module that triggers when opening files. This module is used to improve compatibility between Apple devices and Netatalk AFP servers. “The problem in vfs_fruit exists in the default VFS fruit module configuration using fruit:metadata=netatalk or fruit:resource=file”says Samba.

On the same subject: Windows 10 — beware, this major flaw in Microsoft Defender allows installing malware incognito

Urgently install the latest version of Samba

According to Samba, this vulnerability would allow hackers to execute malicious code remotelywithout the victim needing to interact. “Note that this can be a guest or unauthenticated user if those users have write access to extended attributes of files”adds Samba, before pointing out that “if both options are set to different settings than the defaults, the system is not affected by the security issue“.

Related: Apple, Amazon, Twitter, and Cloudflare Servers Hit by Worst Flaw in Internet History

The Samba Team therefore strongly advises network administrators to install as soon as possible versions 4.13.17, 4.14.12, and 4.15.5, available from today. These updates close the loophole. Another solution is to delete the term “fruit” in the lines “vfs objects” configuration files. Nevertheless, “Changing the VFS module settings fruit:metadata or fruit:resource to use the unassigned setting causes all stored information to become inaccessible and gives macOS clients the impression that the information is lost. »

Related Articles

Leave a Reply

Your email address will not be published.