Date Discovered April 7, 2003
Description Multiple remote buffer overflow vulnerabilities have been reported for Samba and Samba-TNG. Although unspecified, it is likely that these issues are exploitable by an attacker to execute arbitrary code. All code executed in this manner would be run with the privileges of Samba, typically root.
These vulnerabilities are reported to affect Samba 2.2.8 and Samba-TNG 0.3.1.
** Reports suggest that an automated attack utility may be actively exploiting this vulnerability likely through a bruteforce attack. Although unconfirmed, it may be possible that this may be a worm.
The attack utility has been reported to create several files and drop a trojaned version of the sshd.
Reportedly, the trojaned SSH daemon listens for connections on port 44444.
This attack utility was only observed to be attacking FreeBSD systems however, it is likely that other systems are also affected.
- Compaq Tru64 4.0.0 B
- Compaq Tru64 4.0.0 D
- Compaq Tru64 4.0.0 d PK9 (BL17)
- Compaq Tru64 4.0.0 f
- Compaq Tru64 4.0.0 f PK6 (BL17)
- Compaq Tru64 4.0.0 f PK7 (BL18)
- Compaq Tru64 4.0.0 g
- Compaq Tru64 4.0.0 g PK3 (BL17)
- Compaq Tru64 5.0.0
- Compaq Tru64 5.0.0 PK4 (BL17)
- Compaq Tru64 5.0.0 PK4 (BL18)
- Compaq Tru64 5.0.0 a
- Compaq Tru64 5.0.0 a PK3 (BL17)
- Compaq Tru64 5.0.0 f
- Compaq Tru64 5.1.0
- Compaq Tru64 5.1.0 B
- Compaq Tru64 5.1.0 PK3 (BL17)
- Compaq Tru64 5.1.0 PK4 (BL18)
- Compaq Tru64 5.1.0 PK5 (BL19)
- Compaq Tru64 5.1.0 PK6 (BL20)
- Compaq Tru64 5.1.0 a
- Compaq Tru64 5.1.0 a PK1 (BL1)
- Compaq Tru64 5.1.0 a PK2 (BL2)
- Compaq Tru64 5.1.0 a PK3 (BL3)
- Compaq Tru64 5.1.0 b PK1 (BL1)
- HP CIFS/9000 Server A.01.05
- HP CIFS/9000 Server A.01.06
- HP CIFS/9000 Server A.01.07
- HP CIFS/9000 Server A.01.08
- HP CIFS/9000 Server A.01.08.01
- HP CIFS/9000 Server A.01.09
- HP CIFS/9000 Server A.01.09.01
- HP CIFS/9000 Server A.01.09.02
- HP HP-UX 10.0.0 1
- HP HP-UX 10.20.0
- HP HP-UX 10.24.0
- HP HP-UX 11.0.0
- HP HP-UX 11.0.0 4
- HP HP-UX 11.11.0
- HP HP-UX 11.20.0
- HP HP-UX 11.22.0
- Samba Samba 2.0.0 .0
- Samba Samba 2.0.1
- Samba Samba 2.0.10
- Samba Samba 2.0.2
- Samba Samba 2.0.3
- Samba Samba 2.0.4
- Samba Samba 2.0.5
- Samba Samba 2.0.6
- Samba Samba 2.0.7
- Samba Samba 2.0.8
- Samba Samba 2.0.9
- Samba Samba 2.2.0 .0
- Samba Samba 2.2.0 .0a
- Samba Samba 2.2.1 a
- Samba Samba 2.2.2
- Samba Samba 2.2.3
- Samba Samba 2.2.3 a
- Samba Samba 2.2.4
- Samba Samba 2.2.5
- Samba Samba 2.2.6
- Samba Samba 2.2.7
- Samba Samba 2.2.7 a
- Samba Samba 2.2.8
- Samba-TNG Samba-TNG 0.3.0
- Samba-TNG Samba-TNG 0.3.1
- Sun Cobalt Qube3 4000WG
- Sun Cobalt RaQ 550 4100R
- Sun Cobalt RaQ XTR 3500R
- Sun Cobalt RaQ4 3001R
- Sun Linux 5.0.0
- Sun Solaris 2.5.1
- Sun Solaris 2.5.1_ppc
- Sun Solaris 2.5.1_x86
- Sun Solaris 2.6
- Sun Solaris 2.6_x86
- Sun Solaris 7.0
- Sun Solaris 7.0_x86
- Sun Solaris 8
- Sun Solaris 8_x86
- Sun Solaris 9
- Sun Solaris 9_x86
Block external access at the network boundary, unless external parties require service. Restrict remote access to Samba-based services from all but trusted hosts. This will limit an attacker's ability to exploit this vulnerability.
Run all software as a nonprivileged user with minimal access rights. Where possible, run the Samba server with the least privileges required to function. This will limit the consequences of an attacker gaining the ability to execute arbitrary code.
Modify default ACL settings. Unless anonymous access is specifically required, modify Samba's access control list to prevent connections from anonymous users.
Implement multiple redundant layers of security. The exploitation of vulnerabilities to execute arbitrary code may be hindered through the use of various memory protection schemes. Where possible, implement the use of non-executable and randomly mapped memory pages.
Disable any services that are not needed.
Unless the use of Samba is explicitly required, disable its use completely.
Samba 2.2.8a has been released which addresses these issues. Samba is currently developing patches which will specifically address the problems in version 2.2.7a and 2.0.10. Users are advised to upgrade as soon as possible.
Slackware has released a security advisory (2003-04-08) containing fixes which address this issue.
Debian has released a security advisory (DSA 280-1) containing fixes which address this issue.
OpenPKG has released a security advisory (OpenPKG-SA-2003.028) containing fixes which address this issue.
Mandrake has released a security advisory (MDKSA-2003:044) containing fixes which address this issue.
FreeBSD has released a security note (FreeBSD-SN-03:01) which contains updated ports information. Further information can be found in the attached advisory.
Immunix has released a security advisory (IMNX-2003-7+-006-01) which contains fixes which address this issue for Samba 2.0.10. Users are advised to upgrade as soon as possible.
Red Hat has revised its advisory (RHSA-2003:137-02). See referenced advisory for new fix details.
Gentoo Linux has released an advisory. Users who have installed net-fs/samba are advised to upgrade to samba-2.2.8a by issuing the following commands:
HP has released an advisory HPSBUX0304-254. HP has stated that new smbd binaries (smbd.11.00.r1.gz) are available at the following locations. Further information is available in the referenced advisory:
Veritas has determined that various ServPoint NAS releases are affected by this vulnerability. Patches are currently being developed. Users are advised to contact the vendor for further information regarding how to obtain fixes.
Credits These vulnerabilities were discovered by the Samba team.
Copyright © Symantec Corporation.
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com
are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.