1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml">
6 <title>Samba - Security Announcement Archive</title>
11 <H2>CVE-2013-0214.html:</H2>
15 ===========================================================
16 == Subject: Cross-Site Request Forgery in SWAT
18 == CVE ID#: CVE-2013-0214
20 == Versions: Samba 3.0.x - 4.0.1 (inclusive)
22 == Summary: The Samba Web Administration Tool (SWAT) in Samba versions
23 == 3.0.x to 4.0.1 are affected by a cross-site request forgery.
25 == Note that SWAT must be enabled AND the user's password be known
26 == in order for this vulnerability to be exploitable. By default,
27 == SWAT is *not* enabled on a Samba install.
29 ===========================================================
35 All current released versions of Samba are vulnerable to a cross-site
36 request forgery in the Samba Web Administration Tool (SWAT). By guessing a
37 user's password and then tricking a user who is authenticated with SWAT into
38 clicking a manipulated URL on a different web page, it is possible to manipulate
41 In order to be vulnerable, the attacker needs to know the victim's password.
42 Additionally SWAT must have been installed and enabled either as a standalone
43 server launched from inetd or xinetd, or as a CGI plugin to Apache. If SWAT has
44 not been installed or enabled (which is the default install state for Samba)
45 this advisory can be ignored.
47 If the user authenticated to SWAT as root AND the attacker knows the user's root
48 password, it is possible to shut down or start the samba daemons, add or remove
49 shares, printers and user accounts and to change other aspects of the Samba
52 The Samba Team considers that if the attacker knows the root password, that
53 security has already been breached, but is patching this issue in 4.0.2 out of
54 an abundance of caution, as we are already patching another SWAT issue with this
61 Ensure SWAT is turned off and configure Samba using an alternative method
62 to edit the smb.conf file.
68 Patches addressing this defect have been posted to
70 http://www.samba.org/samba/security/
72 Additionally, Samba 4.0.2, 3.6.12 and 3.5.21 have been issued as security
73 releases to correct the defect. Samba administrators running affected versions
74 are advised to upgrade to 4.0.2, 3.6.12 or 3.5.21 or apply the patch as soon as
81 The vulnerability was discovered and reported to the Samba Team by Jann Horn.
82 The patches for all Samba versions were written and tested by Kai Blin
86 ==========================================================
87 == Our Code, Our Bugs, Our Responsibility.
89 ==========================================================