ID CVE-2010-0926
Summary The default configuration of smbd in Samba before 3.3.11, 3.4.x before 3.4.6, and 3.5.x before 3.5.0rc3, when a writable share exists, allows remote authenticated users to leverage a directory traversal vulnerability, and access arbitrary files, by using the symlink command in smbclient to create a symlink containing .. (dot dot) sequences, related to the combination of the unix extensions and wide links options.
Vulnerable Configurations
  • cpe:2.3:a:samba:samba:3.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.3.7:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.3.8:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.3.9:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.3.10:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:samba:samba:3.5.0:*:*:*:*:*:*:*
Base: 3.5 (as of 09-09-2010 - 05:40)
  • Manipulating Web Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
  • Using Slashes and URL Encoding Combined to Bypass Validation Logic
    This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
  • Using Escaped Slashes in Alternate Encoding
    This attack targets the use of the backslash in alternate encoding. An attacker can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the attacker tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
  • Path Traversal
    An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attacker providing a complete path to a targeted file or using control characters (e.g. path separators (/ or \) and/or dots (.)) to reach desired directories or files.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
cvss-vector via4 AV:N/AC:M/Au:S/C:P/I:N/A:N
redhat via4
id 562568
title default
  • comment Red Hat Enterprise Linux must be installed
    oval oval:com.redhat.rhba:tst:20070304026
  • AND
    • comment Red Hat Enterprise Linux 5 is installed
      oval oval:com.redhat.rhba:tst:20070331005
    • OR
      • AND
        • comment libsmbclient is earlier than 0:3.0.33-3.37.el5
          oval oval:com.redhat.rhsa:tst:20120313001
        • comment libsmbclient is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20100488011
      • AND
        • comment libsmbclient-devel is earlier than 0:3.0.33-3.37.el5
          oval oval:com.redhat.rhsa:tst:20120313003
        • comment libsmbclient-devel is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20100488013
      • AND
        • comment samba is earlier than 0:3.0.33-3.37.el5
          oval oval:com.redhat.rhsa:tst:20120313005
        • comment samba is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20070061002
      • AND
        • comment samba-client is earlier than 0:3.0.33-3.37.el5
          oval oval:com.redhat.rhsa:tst:20120313007
        • comment samba-client is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20070061004
      • AND
        • comment samba-common is earlier than 0:3.0.33-3.37.el5
          oval oval:com.redhat.rhsa:tst:20120313009
        • comment samba-common is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20070061006
      • AND
        • comment samba-swat is earlier than 0:3.0.33-3.37.el5
          oval oval:com.redhat.rhsa:tst:20120313011
        • comment samba-swat is signed with Red Hat redhatrelease key
          oval oval:com.redhat.rhsa:tst:20070061008
id RHSA-2012:0313
released 2012-02-21
severity Low
title RHSA-2012:0313: samba security, bug fix, and enhancement update (Low)
  • libsmbclient-0:3.0.33-3.37.el5
  • libsmbclient-devel-0:3.0.33-3.37.el5
  • samba-0:3.0.33-3.37.el5
  • samba-client-0:3.0.33-3.37.el5
  • samba-common-0:3.0.33-3.37.el5
  • samba-debuginfo-0:3.0.33-3.37.el5
  • samba-swat-0:3.0.33-3.37.el5
refmap via4
  • 20100204 Re: Samba Remote Zero-Day Exploit
  • 20100204 Samba Remote Zero-Day Exploit
  • 20100205 Re: Samba Remote Zero-Day Exploit
  • [oss-security] 20100205 Re: Samba symlink 0day flaw
  • [oss-security] 20100205 Samba symlink 0day flaw
  • [oss-security] 20100206 Re: Samba symlink 0day flaw
  • [oss-security] 20100305 Re: Samba symlink 0day flaw
  • [samba-technical] 20100205 Claimed Zero Day exploit in Samba.
  • [samba-technical] 20100205 Re: Claimed Zero Day exploit in Samba.
  • [samba-technical] 20100205 re: Claimed Zero Day exploit in Samba.
  • [samba-technical] 20100206 Re: Claimed Zero Day exploit in Samba.
  • [samba-technical] 20100207 Re: Claimed Zero Day exploit in Samba.
secunia 39317
  • SUSE-SR:2010:008
  • SUSE-SR:2010:014
Last major update 09-09-2010 - 05:40
Published 10-03-2010 - 20:13
Last modified 09-09-2010 - 05:40
Back to Top